Microservices
summary
Claims outcomes from ~50 projects show microservices reduce code size, enable independent deploys and let teams swap components without breaking others. Example: a delayed tweet service is added by sending an extra field while the original service simply ignores unknown message fields. Communication relies on messages with routing via fan-out HTTP chains or smarter queues/filters; trade-offs include added latency for near-unlimited throughput. Tools used in practice: Node.js, Redis, Docker plus custom deployment tooling; common mistakes: leaving business logic in the web server and premature language heterogeneity.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:06Why Why Do Microservices Make You Feel So Cool
- 7:25How Do You Root Messages to the Right Place
- 7:36Message Routing
- 12:11Deployment
- 13:08Original Schematic Diagram for Charles Babbage's Analytical Engine
- 20:49Optical Illusions








