Infrastructure as Actual Code
summary
Argues that cloud automation becomes executable application topology not just server provisioning, using AWS CDK plus Lambda, Step Functions, EventBridge, SNS, SQS and DynamoDB to turn Enterprise Integration Patterns into deployable constructs. Builds a mortgage-broker example that wires orchestration, fan‑out/aggregate and filters via message filter and content filter, attaches Lambda destinations for composition, and exposes business‑level parameters as code. Shows automation as a domain language that generates CloudFormation but keeps abstractions intact so topology is Infrastructure as actual Code.
AI-written summary · about
chapters (5)
- 0:00Start
- 13:34Declarative provisioning
- 27:58Serverless automation
- 30:22The Integration Patterns Loan Broker (2003-2022)
- 41:14Encoding Integration Patterns with CDK
related talks
32mInfrastructure From Code: Next up for DevOps?
24mInfrastructure as Code on AWS
44mInfrastructure as Software
42mInfrastructure as Code - Lessons learned from Dev to Ops
53mInfrastructure *is* Code with the AWS Cloud Development Kit
28mAutomate everything with CDK in AWS
36mStop configuring infrastructure, start coding it!
19mInfrastructure as Code: A Must Know Skill for Today's Developers
