Multi-Tenant Architecture

[pantheredeye]

I initially took the approach - do things that don't scale. With that in mind, I was going to set up subdomains and new servers for every tenant that I onboarded early. Now, with the app live - I would 1) really like to avoid that and 2) try to implement multi-tenancy early to keep from minimizing headaches in the future.

I have to say, this topic is where my projects go to die. When I think about multi-tenancy my mind sees blackness. Any help or guidance is extremely welcome.

Currently, looking here for use of directives in a redwood project.

and Brandon's article for discussion on the architecture of linear model.

In the Linear model, a user can both have separate user accounts for different organizations and have access to multiple organizations from a single account.

The Linear model combines the best of GitHub and Google and is ideal for most B2B startups because it supports both enterprise and small companies using consultants. Enterprises can both strictly control user provisioning and access and allow their users to belong to multiple organizations. It is the most flexible, and it provides the best user experience because it reduces the number of logins required to access all their organizations.

I recommend the Linear model for most startups. You need to really know what you are doing and why you are doing it before choosing the GitHub or Google models.

[pantheredeye]

I guess this doesn't even start to get to permissions management. One step at a time?! I'm thinking start simple with a version of RBAC and move into ABAC if needed over time.