The Philosophy of Microservice Design with ServiceTalk.io
summary
The talk explains how ServiceTalk (a reactive Java library) addresses common problems when building reactive microservices: thread and data-flow management, environment integration, reliability and scalability. It describes ServiceTalk’s design philosophy of providing low-entry abstractions, richer features, and APIs that boost developer productivity by supporting mixed programming models and simplifying reactive microservice concerns.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:08What is ServiceTalk.io
- 5:36Monolith vs microservices
- 8:23Why Netty
- 13:43Beyond Netty alone
- 19:24Reactive Streams need
- 26:33ServiceTalk principles
- 32:15ServiceTalk APIs
- 37:53Blocking calls problem
- 46:27App evolution example
- 57:28ServiceTalk features
- 1:03:50Getting started
- 1:10:59Summary
related talks
23mLightning Talk: Rethinking Microservices
24mBringing Reactive Programming to Java and Microservices
30mReactive Microservices
49mKeynote
48mReactive Microservice in Action
54mThe Long Sad History of Microservices
48mDesign principles to the rescue of micro-services
14mSAG Expert Interview #05: The Evolution of Microservices