Microservices: A Tale of 3 Heroes
summary
Three companies migrate at different paces: GitHub extracts auth from a 13‑year Rails monolith, builds microservice-in-a-box provisioning, uses Hubot deploy trains but still hits multi‑hour deploy queues and survives with HMAC endpoints while planning a service mesh; SendGrid runs Kafka for durable messaging, adopts Envoy sidecars and a gateway of gateways hybrid to keep rate limits consistent across DC and AWS; Catalyst fixes Sidekiq by storing IDs instead of payloads, spins up a duplicate cluster with a router, and peels auth and routing out of the monolith.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:26Introduction
- 1:59A Hero's Journey x 3
- 2:50Before our story begins...
- 12:03Where we are at
- 13:43SendGrid Mail Pipeline
- 14:42Bloat problems
- 15:36Compliance problems
- 16:12Load problems
- 17:10Data Contracts and Data Isolation
- 18:10Service Mesh Gold Standard
- 18:55Gateway of Gateways
- 23:12Constraints (a quick recap)
- 24:01Catalyst's Transformation
- 27:18Summary & Key Takeaways
related talks
52mMicroservices: A Utopian Mystery
33mAdventures with Micro Services in Rails
01h 01mMicroservices Gone Wrong
27mScaling a Rails Monolith w/Event Driven Microservices
23mMicroservices – Sean Smith
10mMicroservices, Messaging, and Failure: How Simplifying Our Architecture Saved Us
43mGo micro with Microservices
44mMicroservices - How to create problems by solving problems?