Microservice Architecture with Reusable Components
summary
Describes using Node.js, Docker and RabbitMQ to build microservice fleets composed from reusable private npm packages, published to Nexus and shipped as versioned Docker image artifacts. Recommends an ECB (boundary-control-entity) pattern, following the 12‑factor principles, enforcing private packages, and generating boilerplate with Yeoman/plop to standardize repo layout and CI so teams avoid copy‑paste and reduce DRY rot.
AI-written summary · about
chapters (12)
- 0:00Microservice intro
- 3:08Reusable components
- 7:05Microservices not reusable
- 10:16Developing reusable components
- 15:35Component repo & CI/CD
- 20:29Docker & infra deployment
- 21:09Logging & monitoring
- 22:13Switching from monolith
- 23:17BCE architecture patterns
- 31:44App init & shutdown
- 33:13Reusable components summary
- 34:20Q&A
related talks
22mRapidly Developing Microservices with Node js and Docker
47mDivide and Conquer – Microservices with Node.js
29mNode Microservices - the definitive guide
43mPatterns for Reactive node.js Microservices
48mMicroservices with NodeJS
27mProgressive Microservices with NodeJS
31mDeveloping Microservices with NestJS
34mMicroservices using Node.js and RabbitMQ