Patterns and Practices for Real-world event-driven microservices

on YouTube ↗38m

" summary

Jet.com designs an event‑driven platform with 300–350 microservices, processes ~20,000 orders/day (growth from hundreds), and relies on Azure and F# while embracing event sourcing and immutable data. Key concrete practices: isolate side effects, use a staging backup service to replay events, one YAML per service for runtime config, and a homegrown runtime Torch: 30s deploy that cuts deployment from ~15–20 minutes. These practices prove practical and repeatable in production.

AI-written summary · about

" chapters (12)

1. 0:00Intro
2. 0:33Taking on Amazon!
3. 5:51Does anyone here use Rx?
4. 6:36Event-sourced
5. 9:33Don't abstract
6. 10:46Be functional!
7. 13:18Isolate side effects
8. 15:14Use a backup service to replay events
9. 17:00What do our services look like?
10. 24:23Microservices should not control own lifecycle
11. 27:23Torch YAML files
12. 29:31Summary

" related talks

• 55mPatterns and practices for real-world event-driven microservicesRachel Reese · NDC Sydney 2016
• 26mImplementing Event-Driven Microservices Architecture (...)Nikhil Barthwal · Lambda Days 2017
• 01h 07mMicroservices from the Trenches. A Guide through the Architecture, Design, CodeSander Hoogendoorn · Software Architecture Gathering – Digital 2023
• 01h 08mEvent Driven Architecture – Enabling MicroservicesBrad Irby · Silicon Valley Code Camp 2018
• 45mMicroservices: A retrospectiveTomer Gabel · Øredev 2019
• 48mChallenges in Implementing MicroServicesFred George · Agile Singapore Conference 2016
• 41m.NET Microservices in Real LifeSerhii Radzyniak · .NET fwdays'17
• 58mMicroservices at Scale - ASP.NET Core, Service Fabric, and Azure in productionLouis DeJardin · NDC Sydney 2017