Building Multi-Tenant SaaS Architectures

Chapter 9. Tenant Isolation

I’ve referred to the concept of tenant isolation throughout my coverage of the different multi-tenant architecture constructs, patterns, and strategies. Our prior glimpses of this topic stayed mostly high level and conceptual, highlighting how isolation is used to ensure that one tenant can’t access the resources of another tenant. Now, however, it’s time to dig squarely into the details of tenant isolation and look at concrete mechanisms that are used to apply isolation across the different layers of your SaaS architecture.

In this chapter, my goal is to distill the nuances of tenant isolation into a set of terms, patterns, and practices that will provide you with a better framework for thinking about how and when you should be introducing tenant isolation mechanisms into your architecture. I’ll start out by establishing a clear view of the role of tenant isolation and the foundational concepts that shape your approach to building a tenant isolation strategy.

From there, we can then start to look at the layered nature of tenant isolation, identifying the different areas within your architecture where you would consider introducing mechanisms that will prevent cross-tenant access. This will give you a better sense of the nuances and considerations that come with creating an isolation model for the different technologies and infrastructure constructs that are part of your multi-tenant environment. This will also highlight some of the challenges and advantages ...