Patterns for Reactive node.js Microservices
summary
Node.js microservices publish product events that let many services subscribe and maintain local state so the system handles 80 million products per day with resilience and no global bottleneck. Deployment uses Docker, Kubernetes, CI and per-component domain packages with schema validation via NPM so interfaces break fast. Teams start with a walking skeleton and migrate legacy tables by publishing deltas. Code embraces a crash-only design, avoids generic try/catch, employs extensive monitoring and consistency probes, and reports that the architecture scales and recovers in practice.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:13The Reactive Manifesto
- 7:57Resilience
- 12:12Basics
- 12:55Know Your Weaknesses
- 14:12Walking Skeleton
- 26:43Reactive Facade
- 27:55Monitoring is the unit testing of dynamic systems
- 29:06Collect patterns
related talks
27mProgressive Microservices with NodeJS
44mMicroservices - the lean way (NodeJS)
29mNode Microservices - the definitive guide
51mCompetitive retail architecture with microservices
40mMicroservice Architecture with Reusable Components
52mMicroservices the Lean Way NodeJS
47mDivide and Conquer – Microservices with Node.js
22mRapidly Developing Microservices with Node js and Docker
