Tod Golding

The SaaS Builder Toolkit (SBT) provides developers with a pre-built set of tools that decompose SaaS into a series of building blocks that can be used to create multi-tenant environments.

This session provides AWS Partners and chief technologists a look at how Amazon is using generative AI to continually innovate and develop solutions that drive value for our partners and customers.

There is no one-size-fits-all SaaS architecture. Instead, architects must find the unique mix of multi-tenant strategies that address the needs of their specific application.

Building a multi-tenant SaaS architecture is a balancing act. Finding the right blend of cost efficiency, scale, resilience, and operational agility can be challenging.

Cost plays a key role in driving the growth strategies of SaaS companies. Multi-tenancy requires teams to think beyond the basics of auto scaling, enabling creative strategies that allow their architecture to support a myriad of complex cost-scaling challenges.

In this chalk talk, discuss customer stories, best practices, and architectures for building SaaS solutions with serverless functions and container technologies. Dive deep into common challenges and how to sidestep them with a serverless-first mindset.

A SaaS architecture must be able to support shifting workloads, complex scaling policies, isolation and a host of other multi-tenant considerations. You need to understand how your system will react and respond to these challenges.

SaaS workloads present builders with a unique blend of architecture challenges. Teams are constantly searching for strategies, policies, and deployment models that allow them to address shifting multi-tenant consumption patterns across different geographic, performance, and activity profiles.

There are a broad range of considerations that go into designing a multi-tenant architecture. The realities of your environment, the needs of your domain, the isolation requirements of your tenants, the identity model of your solution—they are all areas you should explore when building a SaaS solution on AWS.

Amazon EKS provides SaaS developers with a rich collection of constructs that can be used to compose a SaaS architecture. Navigating the mix of multi-tenant Amazon EKS patterns and strategies can be challenging.

In this chalk talk, consider and discuss customer stories, best practices, and architectures for building SaaS solutions with serverless and container technologies. Dive deep into common challenges and how to sidestep them with a serverless-first mindset.

Building and delivering a multi-tenant solution is a good start. However—even after it’s up and running—you should be continually looking at ways to optimize your SaaS environment, identifying opportunities to refine your solution and maximize the operational efficiency, growth, agility, and innovation of your SaaS offering.

SaaS architecture varies across domains, stacks, and customer requirements. However, there are well-defined patterns that must be addressed by every SaaS solution.

Amazon EKS provides SaaS developers with a rich collection of constructs that can be used to compose a SaaS architecture. Navigating the mix of multi-tenant Amazon EKS patterns and strategies can be challenging.

AWS SaaS Boost provides developers with a ready-made, open-source model for building and operating SaaS solutions on AWS. In an effort to enrich this offering, AWS plans to add support for a more diverse range of SaaS architectures, extensibility options, and third-party integrations.

The serverless SaaS model presents architects and developers with a range of new multi-tenant design considerations. How do you implement tenant isolation in an AWS Lambda environment?

Serverless and SaaS represent a natural match. The serverless model enables SaaS providers to create solutions that align with the shifting profile and needs of multi-tenant environments.

Amazon EKS is compelling for SaaS providers, enabling operational, cost, scale, and agility goals that are common to SaaS environments. It also introduces a new collection of constructs that influence how you decompose, isolate, deploy, and manage your architecture.

Many organizations begin their journey to SaaS with a single-tenant monolithic architecture. Their goal is to transform these systems into modern, multitenant serverless systems that can realize all of the cost, scale, and agility benefits that SaaS environments demand.

The move to a SaaS delivery model can be daunting for ISV developers and architects. To target this need, AWS has created an open-source solution that can jump-start your path to SaaS.

While the rationale for adopting a microservices architecture is well-understood, selecting the right size and scope of your microservices can be challenging—especially in SaaS environments. SaaS microservices must consider your multi-tenant isolation boundaries, your data partitioning requirements, your multi-tenant scaling profile, and your tiering strategy.

Metrics are at the core of every SaaS business. Having your finger on the pulse of tenant and system activity is essential to achieving and maintaining scale, agility, and innovation.

The emergence of serverless infrastructure and services represents a fundamental shift in how developers approach architecting applications. This is especially relevant in the world of SaaS, where systems must efficiently and cost-effectively respond to continually shifting multi-tenant loads and profiles.

As SaaS organizations grow and extend their reach into new markets and geographies, this often triggers the move to a multi-region model where their SaaS offering must be configured and deployed to run in a more distributed model. This move to a multi-region model adds a new layer of complexity that can easily undermine the agility of and organization’s SaaS offering.

Migrating an existing single-tenant solution to a multitenant SaaS model can be challenging. Finding a migration approach that somehow balances the ongoing needs of the business with the market, cost, and competitive pressures of getting to SaaS often requires teams to identify creative migration strategies.