Operating EDA with Quality in Mind
summary
Argues that end‑to‑end CI tests are often too slow and brittle for evented systems, so teams deploy real AWS EventBridge and SQS test hooks, invoke APIs or Step Functions, then use the AWS SDK to query DynamoDB or describe executions with recursive backoff retries to avoid flakiness. Recommends mocking unreliable third parties (WireMock or similar) only when worth the overhead, focusing on test only critical paths and using an EventBridge+SQS test harness plus concise dashboards, alerts, traces and logs for fast recovery.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:04Agenda
- 4:15What modern systems require
- 10:00Elements of EDA
- 14:05EDA challenges
- 18:56Handling the challenges
- 42:21Role of QA in serverless
- 45:50Outro
related talks
43mBest practices for continuous testing and observability
49mJourney to EDA: Patterns, Best Practices & Practical Tips
38mEvent-driven Architecture
43mIntegration testing a cloud native application with JavaScript｜
39mWhat Can Go Wrong With Testing an ETL Pipeline?
56mDesigning Event-Driven Applications to Improve Scalability
12mConvergent Quality Engineering
13mAWS for Testing – Top 3 Use Cases