What's changed: Deepened SAP-C02 Chapter 4 (added comparison tables, scenarios, FAQs, exam traps, deep-dive paragraphs to each section; localized figures to Japanese)
4.3Modernizing on the Cloud
Understand post-migration modernization—containers (ECS/EKS/Fargate), serverless, decomposing into microservices, and incremental migration via the strangler fig pattern. Improve agility, scale, and cost-efficiency.
Modernization moves a monolith to containers/serverless and decomposes it into microservices—done incrementally, not all at once.
4.3.1Modernization patterns
- Containers: EKS (Kubernetes) / ECS (AWS-native); use Fargate for no server management.
- Serverless: Lambda for small event-driven functions; scales with zero infra management.
- Microservices: decompose the monolith by capability for independent deploy/scale.
- Strangler fig: run old/new behind a router and shift features gradually to new services, retiring the old last.
Common on SAP-C02: Kubernetes required = EKS, AWS-native containers = ECS, no-server-management containers = Fargate, event-driven functions = Lambda, safe incremental monolith migration = strangler fig pattern. Big-bang rewrites are risky; incremental migration is preferred.
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.