Setting the file. One moment.
Skill 24 · Architect For Startups
Subchapter 24.26
references/rapid-patterns.mdMarkdown2 KBView on GitHub
Opinionated architecture choices for startups. These differ from standard AWS guidance.
These are the specific signals to move from the rapid/cheap pattern to something more robust:
| Signal | Action |
|---|---|
| Lambda hitting 15-min timeout | Move that workload to Fargate |
| >1000 concurrent Lambda executions | Consider Fargate for steady-state traffic |
| DynamoDB costs > $100/month | Evaluate access patterns, consider provisioned mode |
| Need complex SQL queries | Add Aurora Serverless v2 alongside DynamoDB |
| Multiple teams deploying to same service | Split into separate services with clear APIs |
| Customers asking about SLAs | Add multi-AZ, health checks, monitoring |
| >100GB of analytics data | Graduate from Athena+S3 to a data warehouse |
| >10 tenants with isolation requirements | Graduate from Lambda+DynamoDB to Fargate+Aurora |
InvokeModel directly is simpler and cheaper.