3 ms·
The highest level entry point makes so much sense. I’ve been building multitenant saas for last 3 years enforcing “where tenant = x” and you’ve just blown my mi
by HatchedLake721 6y ago
The highest level entry point makes so much sense. I’ve been building multitenant saas for last 3 years enforcing “where tenant = x” and you’ve just blown my mind.
- hackerm0nkey 6y agoOn more than one occasion I've started with a simple table for all tenants (where tenant = x) because we didn't know at the time if we will have many. Then progressively when we understood how the service will be used, refactored to keep separate tenant's data separate. Ended up with each tenant in a given schema, we were using Java and relied on Hibernate (ORM) to help connecting to the correct DB (it does support multi-tenancy) as well as on a DB migration tool (Liquibase) so any changes we made to the schema get replicated over all tenants.
- thrownaway954 6y agothat's why we're here... learning something new everyday is a great things. now imagine how cool it will be implementing this is your projects from here out :)