3 ms·
On the surface, you are right. However you often still need custom code to handle the business logic. If a new customer joins you have spin up a new instance. I
by rpedela 10y ago
On the surface, you are right. However you often still need custom code to handle the business logic. If a new customer joins you have spin up a new instance. If a customer leaves then you have to delete the instance. How do you automate backup and restore? Is there a central repo for record keeping and how does that updated?
Sometimes multi-tenancy is a simpler solution because no instance fleet management code needs to be written. With everything there are downsides to multi-tenancy too so you have to weigh the pros and cons for the specific project.
- Walkman 10y agoYou are right. Without multitenancy, you have to write the automation code, however, it's much better IMO, because with multitenancy, you have to think about tenancy ALL THE TIME not just that one time. So I think overall it's a better trade off and still less code and less problems to solve and easier to solve.