Click any service node to inspect it — watch async paths diverge after the Lambda handler
All infrastructure provisioned with AWS CDK (TypeScript). Zero servers to patch. Need something similar built? · See the Kafka architecture →
About this demo
This visualiser shows a typical AWS serverless request path: API Gateway receives an inbound call, routes it to a Lambda function, which fans out to downstream managed services — S3 for object storage, DynamoDB for low-latency reads, SQS for async processing, and SNS for downstream notifications. Each hop is animated with realistic latency to illustrate where time is spent in a real request.
Serverless architecture eliminates the need to provision or manage servers. Lambda scales automatically from zero to thousands of concurrent invocations, with billing per 100 ms of execution. The primary engineering challenge shifts from capacity planning to cold-start latency, IAM permission design, and keeping function packages small — especially relevant when running Spring Boot inside Lambda.