Effective Data Synchronization between Rails Microservices
summary
Claim: a Kafka-based message bus lets data engineers produce Avro-validated operations and Rails apps consume them through importers that run real domain logic, with per-app topics, batching, permitted-attribute checks, and backpressure controls. Producers often run Python jobs that write Avro-validated operations into batches; consumers map model+type to importers and return operation results. The system yields 7.7 billion data updates since April 2019 and proves Kafka-based message bus and per-app topics scale and preserve Rails callbacks.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:58Agenda
- 2:34Company Background
- 5:00Effective Data Synchronization
- 5:46Data Updates
- 9:15Data Needs
- 9:58Example
- 12:55The Pinky Promise
- 19:09The Growth
- 24:44Operations
- 26:29Batching
- 28:09Data Producers
- 31:39App Consumers
- 35:39Summary
related talks
35mSo You’ve Got Yourself a Kafka: Event-Powered Rails Services
11mSpinning up micro-services using Ruby/Kafka
31mEvent Streaming on Rails
27mEvent Streaming Patterns for Ruby Services
11mSpinning up micro-services using Ruby/Kafka
33mI Can’t Believe It’s Not A Queue: Using Kafka with Rails
30mSome Funny Things Happened on The Way to A Service Ecosystem
42mSimplifying Logs, Events and Streams: Kafka + Rails
