Elevating Event-Driven Architecture: Boost your delivery with AsyncAPI and Microcks
summary
Microcks consumes AsyncAPI files to generate mocks and tests on real brokers, creating a WebSocket endpoint that emits an order event every ~3s and auto-creating an SQS queue (demo shows 27 messages queued). Tests connect to SQS, find the expected two messages and report schema conformance; removing the required status field produces a failing test. Shows generative AI samples, SQS + WebSocket bindings, CI/CD hooks and test‑container libraries for local unit tests.
AI-written summary · about
chapters (21)
- 0:00Event-driven architecture challenges
- 2:12Event-driven APIs in distributed systems
- 4:41Distributed monoliths and versioning risks
- 6:54Microcks for API mocking and testing
- 9:23Microcks architecture and open-source
- 10:26Contract examples and executable specs
- 11:49Multiple protocols with Microcks
- 13:57Mocking and testing benefits in EDA
- 15:01Live demo setup for pastry API
- 16:07Importing AsyncAPI specs into Microcks
- 17:13AI-assisted mock data generation
- 18:18WebSocket mocking for frontend
- 19:04SQS binding for event propagation
- 20:14Multi-protocol message mocking
- 21:41Conformance testing for messages
- 23:30Message compliance against schema
- 24:59Tests in CI/CD pipelines
- 26:06Microcks in unit tests
- 27:10EDA maturity with Microcks
- 28:12Summary and closing
- 28:32Q&A on schema conformance
related talks
30mSpeed Up Your API Deliveries with Microcks
42mAsyncAPI Recipes for EDA Gourmet
22mStrategies for Generating Dynamic, Realistic Mocks for Messaging APIs
50mContinuous API Mocking and Testing with Microcks, Keptn, and Testkube
26mStreamlining Cloud-Native Development: Simplifying Dependencies and Testing with Microcks
21mUsing the AsyncAPI Ecosystem for your Event-Driven Architecture
43mDesigning Event-driven architectures with AsyncAPI
37mRethinking How We Test Our Async Architecture