What should the system boundaries look like?
Use this hub when you are deciding between service shapes, asynchronous boundaries, state placement, or multi-account and multi-region strategy.
Topic hub
Architecture decisions, service boundaries, and production patterns for building serious systems on AWS.
Questions this hub should help answer
Use this hub when you are deciding between service shapes, asynchronous boundaries, state placement, or multi-account and multi-region strategy.
Look here for articles that go beyond “service A vs service B” and into blast radius, failure isolation, and operational cost.
If the decision is still architectural rather than implementation-level, move into the architecture library and then come back for deeper reads.
Browse architecturesStart here in this topic
Open one article that gives the clearest view of how this problem space behaves in production, then continue into the wider set below.
Most CDK tutorials stop at 'it deployed.' This one covers the full aws cdk web application deployment stack - VPC isolation, Fargate on private subnets, Aurora with KMS, CloudFront, Secrets Manager rotation - and the six operational gaps that will wake you up at 2am if you skip them.
Within this topic
These pieces stay inside the same operating surface and are better for depth once you already have the context from the spotlight read.
Continue from here
Go back to Start Here if you want the best cross-topic entry points rather than staying inside a single hub.
Open Start HereCase studies and failure breakdowns are where the publication shows how decisions behave under delivery and production pressure.
Read case studiesConsulting is for architecture reviews, cost teardowns, and AI infrastructure assessments that need direct judgment instead of more reading.
View consulting