Reactive with Apache Thrift + Project Armeria: How WebFlux Was Bolted On without REST

In Victor's team there are about 200 microservices on Apache Thrift. Initially, they were made in sync. As the product evolved, the workload grew, and they ran into a problem: some services can't handle it.

• Why doesn't scaling help in this situation?
• How does project Armeria help?
• What are the pitfalls and drawbacks?
• Is it worth using a reactive approach and when?

The speaker will describe his experience and results.