Reactive Stuff with Apache Thrift + Project Armeria: How WebFlux Was Wired In Without REST
summary
A team migrated about 200 synchronous Apache Thrift microservices toward a reactive model using Project Armeria to handle growing load that some services could not sustain. The talk explains why horizontal scaling alone failed, how Armeria can introduce non-blocking/reactive handling for Thrift services, and discusses pitfalls, drawbacks, and when a reactive approach is (or isn’t) worth adopting.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:01Sync microservice problems
- 10:21Failures and architecture
- 17:20Reactive approach choice
- 20:40Apache Thrift + Armeria integration
- 27:09Reactivity transition challenges
- 32:49Logging and error issues
- 35:43Armeria pros and cons
- 37:39Implementation results
- 38:43Q&A
related talks
30mReacting to the future of application architecture
49mReactive Spring
59mSucceeding at Reactive Architecture
52mReactive Programming with Spring Webflux
46mGet Reactive! Programming, Systems, and Microservices
55mThe Reactive Revolution
38mAdvanced API Design for Scalable Distributed Systems
49mNowadays Architecture Trends, from Monolith to Microservices and Serverless