Conventions Between Applications
summary
A three‑and‑a‑half year effort builds a distributed Rails system of 18 Rails applications with a shared directory encoded in the atlas gem (protobuf schemas) for resource ownership and versioned API contracts. Events go over RabbitMQ with an internal publisher and action_subscriber for Rails‑style subscribers to decouple services; trebuchet performs chunked rolling deploys so teams deploy many small changes with near zero downtime. Concrete tools and semantics are proven in production.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:47Sample Project
- 4:03Atlas - The Directory
- 13:45Events
- 22:264 Tasks???
- 23:46Deployment Costs
- 24:37Zero-Downtime Matters
- 25:58Trebuchet
related talks
27mScaling a Rails Monolith w/Event Driven Microservices
16mOne Ruby App to Rule Them All
43mRails services in the walled garden
42mHow Rails fosters a diverse and competitive tech ecosystem in the era of big tech
34mCarson: On the Path from Big-Ball-of-Mud to SOA
32mRefactoring Legacy Apps with APIs and Messages
23mAbstracting a Service - A Case Study in Forward Thinking with SOA
30mSome Funny Things Happened on The Way to A Service Ecosystem
