SaaS Migration: Moving From Single-Tenant to Multi-Tenant on AWS
summary
Three concrete migration patterns and their tradeoffs: silo lift-and-shift clones one VPC per tenant for fastest time to market but higher ops cost; layered migration pools the web tier (and optionally app tier) to reduce footprint while keeping per-tenant databases; and service-by-service (strangler) carves microservices (Lambda, API Gateway, S3 SPA, ALB) with tenant isolation for long-term agility. Routing options include subdomain DNS or JWT-based routing, and shared services handle onboarding, metrics, billing, and DevOps automation.
AI-written summary · about
chapters (15)
- 0:00Intro
- 2:07The migration challenge
- 3:05Many architectures, one mindset
- 7:09Multiple migration targets
- 8:56Common migration models
- 10:17Silo lift-and-shift migration
- 12:58Tenant routing techniques
- 14:46Silo lift-and-shift sample architecture
- 15:57Unified management and shared services
- 17:10Layered migration (Phase 1)
- 22:39Service-by-service migration (Variation 2)
- 24:33Service-by-service sample architecture
- 25:20No shortcuts for new microservices
- 26:12Migration model pros and cons
- 27:49Takeaways
related talks
28mSaaS migration and modernisation
44mBuilding a serverless multi-tenant SaaS application
29mJourney through the center of migrations
22mFireside Chat with AWS
42mPatterns in using AI/ML to build a SaaS product(ARC302)
32mDive into technical decisions from successful migrations
42mPatterns of a Migration Journey
49mServerless Architectural Patterns and Best Practices