Building multi-Tenant Saas Architectures
The first chapter, or even the first two chapters, of this book are very interesting from my point of view. However, as it progresses, it loses steam because the author essentially keeps repeating that one must account for the ‘multi-tenant’ constraint everywhere.
In summary, you either vertically split each layer so that each separation corresponds to a tenant, or within a given layer, you handle the multi-tenant aspect. For instance, in the case of the database, consider a table for articles: you could either create one schema per tenant (in this case, a merchant) or have a single table containing all articles with an additional tenantId column.
Each decision must account for deployment constraints, load, security, etc. Overall, it’s a somewhat tedious read in the end.
