Reactive Oriented Architecture with Grails
summary
Argues that replacing monoliths with reactive microservices yields real gains: Grails/Groovy services use RabbitMQ for async messaging and Reactor/Akka/RxJava for nonblocking flows, letting order processing decouple from billing and scale independently. Case specifics: Twitter moves from hundreds to 10–20k requests/second per JVM, peaks shown at 5,700 (and 143,199 tested), Netflix runs Chaos Monkey for resiliency, a retail startup uses agent-driven data and reports 30–50% product sell‑through increases while agents earn about $20/hr.
AI-written summary · about
chapters (8)
- 0:00The monolithic problem
- 10:05Shattering the monolith
- 23:41Reactive principles
- 38:12Reactive microservices
- 42:50Practical development tips
- 51:46Groovy reactive tools
- 1:00:34Microservices caveats
- 1:06:41Case studies and conclusion
related talks
40mReactive programming: lessons learned
01h 01mReactive web services
56mReactive programming lessons learned
47mReactive Spring
46mGet Reactive! Programming, Systems, and Microservices
35m5 Reasons to Use Reactive Programming if You Are Not eBay
40mREACTIVE A New Hope! Learn From a Performance History
06mPhil Clay at SpringOne 2020