Re:Our Multi-Tenancy Journey with Postgres Schemas and Apart...
by ozgune on Tuesday December 06, 2016 @12:03PM
(#13116169)
Compared to the one database per tenant method, this approach scales to more tenants with fewer resources. In particular, you're now asking the database to manage HW/SW resources (cpu, ram, disk, network, and OS resources) for your tenants, instead of allocating those resources to different databases yourself.
[ Parent
| on HN ]
There are no comments on this comment yet.