Implementing distributed design patterns on AWS
summary
Shows how to apply bounded context to constrain generative AI by enforcing inter-service contracts and DTO-like context so generated code or plans don’t override core models, demonstrates saga orchestration for validation/retry using AWS Step Functions as a serverless orchestrator, and builds an event-sourced pipeline (MSK/Kinesis event store → Lambda → S3) with CQRS so you can add a vector DB or search index later without changing write logic. Uses Amazon Bedrock, Amazon Q/CodeCatalyst previews and rapid prototyping; prototypes work end-to-end.
AI-written summary · about
chapters (6)
- 0:00Introduction to distributed patterns
- 4:25Bounded context with generative AI
- 10:26Saga orchestration explained
- 18:09Starting simple with data storage
- 20:34Event sourcing and CQRS
- 30:10Future-proofing with patterns
related talks
44mBuilding Distributed Applications with Event-driven Architecture
32mEvent-Driven & Multi-Agent Architectures for Gen AI Workflows
49mBuild modern data architecture and data mesh patterns on AWS
44mGetting started with Orchestration and Choreography in Distributed Applications
29mApplying (D)DDD and CQ(R)S to Cloud Architectures
25mFrom Requirements to Reality: How Solutions Architects Think, Build & Decide
27mBuilding Microservices Architecture The Right Way based on Saga Pattern
56mDesign Patterns for Multi Agent Systems