Microservice in practice with Seneca js
summary
Seneca.js implements microservices by routing JSON messages with pattern matching and swapping transports without changing business code via transport independence. Demo shows a single Node process split to HTTP/TCP, Express/Hapi middleware exposing API routes, and storage plugins (default in-memory). Real project: CoderDojo system with five services (dojo, user, event, badge, Salesforce) supporting ~100 clubs in 60 countries, the event plugin contains 23 patterns. Project dates to 2010 and has ~30 active contributors; Seneca mesh peer-to-peer transport is planned.
AI-written summary · about
chapters (12)
- 0:00Introduction to Seneca JS
- 1:08Why use Seneca for microservices
- 3:40Pattern matching basics
- 6:11Extending business logic
- 8:18Creating and using plugins
- 9:50Scaling with transport independence
- 13:05Choosing transport protocols
- 14:10Connecting APIs to Seneca
- 17:18Handling data in Seneca
- 20:54Real-world case study: CoderDojo
- 25:54Key takeaways and benefits
- 27:04Q&A session
related talks
47mDivide and Conquer – Microservices with Node.js
44mMicroservices - the lean way (NodeJS)
27mProgressive Microservices with NodeJS
48mMicroservices with NodeJS
17mNodejs microservices. From Zero to Hero.
29mDesigning Microservice Architectures
43mPatterns for Reactive node.js Microservices
31mDeveloping Microservices with NestJS
