Nameko for Microservices
summary
Claims that Nameko makes microservices easier to write and test by providing dependency injection, entry points and test helpers; it ships AMQP entry points (RPC and pub/sub), a timer and experimental WebSocket support and recommends AMQP RPC and pub/sub for internal service-to-service messaging. Examples show a memcache dependency and a worker factory for unit tests. Production use at onefinestay (closed source) proves it scales to real workloads; monitoring relies on Logstash, Elasticsearch and Kibana for tracing and analysis.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:56Microservices
- 1:40What are microservices
- 3:22Reasons for adopting microservices
- 4:58Independently deployable
- 5:33Independently scalable
- 6:38Language choice
- 6:54Microservices are not monolithic
- 7:40Conways Law
- 9:19DevOps overhead
- 9:37Microservices are post CD
- 10:40Embrace the domain
- 11:23Decentralize
- 13:23Complexity
- 14:34Questions to Consider
- 14:59Are You Ready
- 15:26Continuous Continuous Spectrum
- 16:07Laker
- 16:55Design principles
- 17:31Code examples
- 19:13Dependencies
- 20:32Extensions
- 22:42WorkerFactory
- 24:23Summary
- 25:53Thanks
- 26:12Question
related talks
27mProgressive Microservices with NodeJS
52m10 LESSONS LEARNED FROM USING KAFKA IN 1000 SCALA MICROSERVICES
28mPractical Microservices, Practical Whiskey
44mLong-lived microservices
27mSimplifying Building and Managing Microservices with Micro
43mGo micro with Microservices
49mPractical Eff monad for microservices
31mHundreds of Microservices without breaking your APIs
