The installation process provisions all of the resources that are part of the baseline environment. The README file provides instructions to deploy the serverless SaaS baseline environment. Platinum tier tenants will have their own dedicated resources. Basic, Standard, and Premium tier tenants will share common set of resources. This serverless SaaS solution uses tiers to determine which model a tenant uses. You can read about these isolation models in the SaaS Tenant Isolation Strategies whitepaper. On the other hand, in the pool model, all tenants share a common storage and compute infrastructure. We’ve included two deployment models in the solution-silo and pool-to highlight how these models can influence the onboarding, isolation, noisy neighbor, performance, and tiering profile of a serverless SaaS environment.įor the silo model, you’ll see each tenant has its own set of infrastructure resources.
Supporting Multiple Deployment Modelsīefore diving into the specifics of this serverless SaaS reference solution, it will be beneficial to outline the different deployment models supported by this experience. You can use this GitHub repository to deploy and explore the reference solution in your AWS account. The reference solution illustrates many of the components needed to build a multi-tenant SaaS solution, such as onboarding, tenant isolation, data partitioning, tenant deployment pipeline, and observability. This includes looking at how you can leverage using Amazon Web Services (AWS) serverless services, such as Amazon API Gateway, Amazon Cognito, AWS Lambda, Amazon DynamoDB, AWS CodePipeline, and Amazon CloudWatch to take advantage of the serverless model. The goal is to explore the architecture and design considerations that went into creating this reference solution. In this post, we’ll look into a reference solution that provides an end-to-end view of a functional multi-tenant serverless SaaS environment. This also reduces the operational overhead and complexity, pushing more of the operational responsibility to managed services. This simplifies the architecture and operational footprint of your application, removing the need to continually chase and manage scaling policies. By removing the notion of servers from your SaaS architecture, organizations can rely on managed services to scale and deliver the precise number of resources your application consumes. These attributes make SaaS a compelling fit for a serverless model. The strategy that works today may not work tomorrow. Finding a mix of scaling strategies that align tenant activity with the actual consumption of resources can be elusive.
This can be especially challenging in a multi-tenant environment where the activity of tenants can be difficult to predict. The move to a software-as-a-service (SaaS) delivery model is accompanied by a desire to maximize cost and operational efficiency. Partner Solutions Architect – AWS SaaS Factoryīy Ujwal Bukka, Partner Solutions Architect – AWS SaaS Factory
0 kommentar(er)
