The modernization of legacy systems with microservices
summary
Legacy monoliths crash when one merchant times out because requests block the single thread pool; the concrete fix is to add Hystrix commands with per-dependency thread pools and circuit breaker behavior, supply simple fallbacks (empty lists), and watch failures flip open on the Hystrix dashboard. For parallel composition use RxJava operators: map, merge, zip and flatMap to combine search IDs with product and inventory calls, run Hystrix-wrapped calls for concurrency, then block once at the end. Start by stabilizing, then apply the strangler pattern to extract services.
AI-written summary · about
chapters (10)
- 0:00Start
- 5:43How Real Production Ready Software Should Look like
- 6:03Timeout
- 6:54Bucket Pattern
- 11:13How To Integrate Hystrix into Your Application
- 16:41History Dashboard
- 21:17Domain Architecture
- 24:43Microarchitecture
- 26:20Strangler Pattern
- 32:03Java Are Reactive Extensions for the Jvm
related talks
41mRxJava & Hystrix - perfect match for distributed applications
44m3 common pitfalls in microservice integration and how to avoid them
29mFault Tolerance is a Requirement Not a Feature - Adar Danait, Lilian Ernest, Citi
59mHow to Escape The Distributed Monolith
48mLost in transaction?
57mSplitting Monolith Application to Microservices
51mBuilding Fault Tolerant Microservices
44mMicroservices - How to create problems by solving problems?