Event Sourcing in Yammer
summary
Yammer prototypes event sourcing for a year, then replaces a Kafka-based pipeline with a managed Azure Event Hubs backend and an in-house RX Java SDK (built on ProtonJ) to hide AMQP offset/failover details. A single “message created” event replaces many RabbitMQ/Rails paths, cutting runtime chattiness and decoupling inbox, group, search and export pipelines. Built tooling includes a consumer lag dashboard and a “hospital” for poison-pill messages; result: faster feature rollout, fewer cross-service failures and smoother operations.
AI-written summary · about
chapters (8)
- 0:00Introduction and team
- 2:57Yammer features and challenges
- 10:38Distributed monolith issues
- 16:36Event sourcing concept and benefits
- 23:15Validation and first implementation
- 27:29Adoption challenges and learnings
- 31:20Workflow complexity and future plans
- 37:42Summary and Q&A
related talks
48mEvent Sourcing - what could possibly go wrong?
52mEvent Sourced Transformation in Financial Systems
52mEvent-driven vs event sourcing: what's really the difference?
49mEvents... And what next?
54mEvent Sourcing
01h 07mAn Architecture with CQRS and Event Sourcing
01h 25mBuilding microservices with event sourcing and CQRS
43mEvent Sourcing dealing with an eventful past