Currently, on my cloud project, I have one database which contains kinds. My question is it possible to create another database that can have different kinds?
Illustration for current database
Currently, it is not possible to create another Datastore database in a single project. A workaround could be using separate projects and adding an authorized IAM user or service account to both projects in order to access both in their respective projects.
Also, maybe a multi tenancy strategy may allow you to customize data values for each tenant, while keeping the same data schema for all of them.
Related
Problem
I have two seperate apps, a "Manager" app and an "Employee" app which share a database, and I am using Firebase for auth. Currently I have two different projects in Firebase, one for each user type. I am now trying to develop a third "Admin" app that allows someone appointed by the organization to manage users on both the "Employee" and "Manager" apps. I have looked into using custom claims but in order for this to work across both apps would have to be on the same Firebase project.
Potential Solutions
Migrate all users to the same Firebase project
In this case, I migrate all of the users to one Firebase project and would assign a type to each user. Upon login, I would check if they are of the right type for that application and log them out if they are not - it's a bit hacky but workable
Switch auth providers
Obviously the most tedious and costly option that I would like to avoid if possible
Can anyone help me figure out the best approach here?
Since all three apps seems to work within the same domain, it'd be most common to set them up in a single project and use custom claims, security rules, or a combination of both to control access of the various user types.
There are multiple companies using one application. So I want to have, or know if this is the best way, to create a project for each company, all this with the Firebase API, to create everything programmatically. But I think this is too difficult to do and get that structure. The truth is that the documentation about the Rest API to create projects is not very clear and I am getting lost. One of the things that I want to structure projects like this is to know how much use is made of each project, calculate requests and use of storage. But I don't know if there are other ways to do this.
It's not possible to create a new project for Firebase using the Firebase API, what is possible is to list projects, and create/list apps within an existing project using the Firebase Management API.
For monitoring usage, you can use Cloud Monitoring to assess the usage of each individual app, per service.
I have to have my security in a different database, because multiple applications use the same security database.
I want to be able in one of my models in a project to reference a user virtually. I can't do this however, since it would create a foreign key relationship over different databases, which is impossible.
I also have a common configuration database where several applications use the same config tables, and have the same problem for the same reason.
What's my best move in this situation?
Thank you.
I am trying to make an asp.net website using Visual web dev and C# that accesses data in an SQL database. For my site, I need to be able to save and access additional user properties such as age and gender. I have been playing around with the built in .NET Login tools but I don't understand how to keep track of the additional properties (age, gender...) I could store all the users information in my own database but how do I correlate the users data in my DB to the usernames in the member database that is automatically created?
Probably profiles are perfect and quite easy to use for your purpose. ASP.NET manages the relation between users and their associated profile data (which you can customize for your needs) quite comfortable. Here is short introduction video:
http://www.asp.net/learn/videos/video-44.aspx
Are you using an ASP.NET website project or web application project? The video (and most information in MSDN) is related to website projects. For web applications there are some complications to take into account when you use profiles.
(Some hints if you are using a web application project:
How to assign Profile values?
If you are using an website project you can ignore this)
As Slauma said ASP.Net Profiles is a great way to do this using the Membership API.
But I don't like the way profiles use delimited list serialized in the database, and I've heard reports of speed issues under heavy load.
I Use Membership API on just about all applications, except for the profile bit.
To store user profiles, you can create a separate table. Maybe called 'UserProfile'. Add a column with a unique index for 'username' and/or 'email'. Which ever you treat as the user's username. Now you can use that column to pull profile information at runtime.
As a bonus, if you use an ORM like Entity framework, you can now write simple LINQ queries to pull your user information.
If i use a separated ASP.NET Membership database what is the correct way to define the relations between the user tables and application data tables?. Should i create copies of the user tables and sync? or is ok to just create the Guid columns and enforce validation in the application code?, Are there any issues with performance that i should be aware of when separating databases?
You can Create two database , one for Membership control and other for Web-site use.
I have Many sites which are running on same concept. No need to worry. web-site will be fast and secure.
If you want to learn more on this or want a live demo then download a classified starter kit for asp.net
Just make the join on databases(with double dots) when you need data.
No need to change, just handle the userid, role etc but need to create two different connection string in your app.
OR Copy the tables in your original db