Re:Our Multi-Tenancy Journey with Postgres Schemas and Apart...
by Walkman on Tuesday December 06, 2016 @08:44AM
(#13114490)
If you are interested in the topic of multi-tenancy, this Microsoft article is the best I ever found: https://msdn.microsoft.com/en-us/library/aa479086.aspx
[ Parent
| on HN ]
Re:Our Multi-Tenancy Journey with Postgres Schemas and Apart...
by why-el on Tuesday December 06, 2016 @11:12AM
(#13115674)
I completely agree. My first professional job was dealing with multi-tenancy, and this article I had printed and sit on my desk for months. Extremely well written.
Re:Our Multi-Tenancy Journey with Postgres Schemas and Apart...
by infogulch on Thursday December 08, 2016 @03:09PM
(#13133805)
If you go with the separate-database model, how do you manage database deployments and syncing it with application deployments?
Re:Our Multi-Tenancy Journey with Postgres Schemas and Apart...
by Walkman on Thursday December 08, 2016 @08:29PM
(#13135940)
Example 1: You can stop all instances and wait for sycn/migration to complete, and start all instances.
Example 2: (which is much better IMO) deploy the new version, but keep the older versions running. Sync/migrate one-by-one and start the new version when ready.