News for hackers. Stuff that matters.
Re:Multi-Tenant Architectures by saberdancer on Sunday August 30, 2020 @03:15PM (#24325143)
How is that multitenant? That's just running a separate instance of application for each tenant.

I agree that it is a completely valid approach, especially if you can afford it, but in my opinion it is just a single tenant application that can be easily spun up. For example, what if you want to manage all of your "tenants" within an admin interface. With a separate instance for all your tenants this is not really possible without additional development or a completely separate admin application.

Re:Multi-Tenant Architectures by social_quotient on Sunday August 30, 2020 @03:44PM (#24325372)
I agree with you here. We typically only advocate for this if the budget/time is low and the likelihood of a next tenant is not soon. Then we learn all we can on the first couple clones and then move to a real multi tenant design while also handling some tech debt we created the first time around.

What tends to happen is a first immediate client is needed along with a couple of sales demo clients. This buys time for the business to see if it’s viable before we bring on complexity.

But I agree clones of a core system isn’t multi tenancy.

For what it’s worth I tend to tell clients we won’t be sustainable after 4-5 of these such clones.

For people considering the clone approach let me caution one issue that comes up about 90% of the time. A client will as for a custom feature and be willing to pay for it for that “one” clone. These divergences are allowed to happen because we aren’t multi-tenant yet. You need to work hard to educate during this phase so you don’t create too much work down the line when you finally consolidate and refactor.

Re:Multi-Tenant Architectures by kissgyorgy on Sunday August 30, 2020 @05:30PM (#24326089)
> How is that multitenant? That's just running a separate instance of application for each tenant.

Exactly! That's the point.