Moving from legacy to event-driven with Kafka
summary
A legacy ERP with business logic in stored procedures is migrated without touching production by observing DB changes, emitting them as events into Kafka append-only log, translating system events to domain events, and replaying into new read models (Postgres, Elasticsearch). Deployment uses Docker and the libRdKafka PHP client; a demo produces 10,000 messages in 0.3s. A strangler-style proxy plus CQRS/event sourcing replaces features gradually, and a proof of concept shrinks an invoicing job from 87 days to 7 minutes.
AI-written summary · about
chapters (13)
- 0:00Start
- 3:53Flexibility
- 4:10Security
- 4:51Dependancy
- 5:29Complexity
- 5:45Costs
- 9:54Stored Procedure
- 18:17Refactor
- 18:40Upgrade Hardware
- 19:21Clone Database(s)
- 19:54Strangler Pattern
- 31:59Producer
- 33:51Consumer
related talks
21mHow Apache Kafka® Generates Value In Retail With Confluent
31mEvent Streaming on Rails
01h 08mEvent Driven Architecture – Enabling Microservices
27mKeynote II: Kafka and the Rise of Event-Driven Microservices
31mEvent driven communication with Kafka on Kubernetes
57mLessons in Building a System that Processes More than 70 Billion Events Daily
42mCreating event-driven microservices: the why, how and what
54mMicroservices with Kafka