Patterns and practices for real-world event-driven microservices

on YouTube ↗55m

" summary

Jet.com runs roughly 700 microservices (est. 400–1,000), puts 90–95% of code in F# (90–95%), and runs on Azure with Kafka/SQL/Blob storage; event-driven and event-sourced architecture is core. Chaos engineering is mandatory, with controlled experiments to design for failure. Microservices are pure data-in/data-out scripts, side effects isolated, and replay uses a staged backup service. A homebuilt Torch lifecycle manager cuts deploys to ~30s and handles YAML-configured scaling.

AI-written summary · about

" chapters (21)

1. 0:00Intro
2. 0:50Jetcom
3. 3:55Microservices
4. 6:40Chaos Engineering
5. 10:38Definitions
6. 13:18Event sourcing
7. 15:46How did Jet decide on microservices
8. 17:34Why did Jet choose Fsharp
9. 22:58How Fsharp helped Jet
10. 23:52Option types
11. 31:14Perl not being readable
12. 37:43Why Fsharp
13. 37:57Shawns Fsharp talk
14. 38:29Be functional
15. 40:09Dont try abstract microservices
16. 41:16Dont do this
17. 41:48Separate them
18. 42:21Staging
19. 48:58Torch
20. 51:07Summary
21. 53:15More information

" related talks

• 38mPatterns and Practices for Real-world event-driven microservicesRachel Reese · Øredev 2015
• 26mImplementing Event-Driven Microservices Architecture (...)Nikhil Barthwal · Lambda Days 2017
• 48mChallenges in Implementing MicroServicesFred George · Agile Singapore Conference 2016
• 01h 07mMicroservices from the Trenches. A Guide through the Architecture, Design, CodeSander Hoogendoorn · Software Architecture Gathering – Digital 2023
• 25mMaking microservices a behaviour not a buzzwordMelissa van der Hecht · apidays London 2019
• 49mChallenges in Implementing MicroservicesFred George · GOTO Amsterdam 2015
• 26mMicroservicesMartin Fowler · GOTO Berlin 2014
• 41m.NET Microservices in Real LifeSerhii Radzyniak · .NET fwdays'17