So do you pick<p>1) Microsoft - ASP - MVC<p>https://www.appseconnect.com/how-to-design-a-multi-tenant-application-with-asp-net-mvc/<p>Or using this guys SassKit<p>http://benfoster.io/blog/saaskit-multi-tenancy-made-easy<p>A Multi-Tenant (SaaS) Application With ASP.NET MVC, Angularjs, EntityFramework and ASP.NET Boilerplate<p>https://www.codeproject.com/Articles/1043326/A-Multi-Tenant-SaaS-Application-With-ASP-NET-MVC-A<p>2) Django<p>http://django-tenant-schemas.readthedocs.io/en/latest/<p>3) Any other approaches?<p>So I would like to know what sort of architectures some startup's have went with, and some of the challenges they hit by picking that approach?
"Multi-tenancy"<p>That term is new to me but after reading a few descriptions I think that CouchDB 2.0 is designed in a way that may provide those capabilities.<p>It has built-in authentication and uses "Users" and "Roles" and "Design Documents" that provide controls and methods to create and access data on a specific database.<p><a href="http://docs.couchdb.org/en/2.1.0/" rel="nofollow">http://docs.couchdb.org/en/2.1.0/</a><p>You might want to look into PouchDB.js as well as the CouchDB Docs.<p><a href="https://pouchdb.com" rel="nofollow">https://pouchdb.com</a>