Service Communication
Event Contracts and Async Integration Lab
Design durable messaging between services with schema evolution, idempotency drills, and replay strategies that match how your buses already behave.
4 days, onsite preferred · Hands-on lab · starts
₩4,100,000 · informational reference only
Program narrative
Participants work through contract-first design for domain events, outbox comparisons, and consumer-driven verification. Labs use representative payloads from commerce and ledger domains without binding you to a single vendor broker.
What is included
- Schema registry patterns with backward compatible change games
- Poison message playbooks and operational dashboards
- SLO drafting for consumer lag and publisher fan-out
- Shadow consumer exercises with synthetic traffic
- Documentation pack for on-call engineers
- Facilitated retro on existing topic sprawl
- Peer review of two real contracts from your organization
Outcomes
- Ship a reviewed event catalog with owners and deprecation notes
- Document replay and compaction policies for two critical streams
- Align on latency budgets between publishers and downstream analytics
Jonah Park
Lead microservices instructor with a background in high-volume fintech pipelines.
Participant questions
Concepts translate across Kafka, RabbitMQ, and cloud-native buses. We do not install vendor software in your production accounts.
Recent participant notes
Event Contracts Lab clarified how our analytics consumers drifted from the checkout stream. The idempotency drills were blunt in a useful way.