Practice focus
We consult on event-driven application programming: defining domain events, choosing delivery semantics, and keeping consumers safe under partial failure.
Typical artifacts
- Event catalog entries with versioning rules
- Sequence diagrams for happy-path and compensating flows
- Consumer checklists (idempotency keys, DLQ routing, poison handling)
- Load and chaos notes for broker failover drills
Stacks we commonly touch
Kafka and managed equivalents, RabbitMQ, cloud vendor queues, and in-process outbox patterns in services your team already runs. We match your observability stack rather than replacing it.
Engagement shape
Discovery call → written proposal with MYR fees → advisory or paired delivery → handover notes for your on-call roster.