Designing a multi-tenant platform: early architectural decisions and their consequences

Early architectural decisions and their consequences Plio was designed to be used by multiple organizations concurrently, each running its own programs, users, and content, while relying on shared infrastructure. This was not a scaling concern discovered later. It was intrinsic to how Plio was expected to be adopted: different organizations…