I love reactive programming. Reactive libraries offer me several tentpole benefits
1. Consistency
2. Smarter, safer concurrency
3. Robustness
4. Resource efficiency
I’ll expand on those points here:
1. Consistency
2. Smarter, safer concurrency
3. Robustness
4. Resource efficiency
I’ll expand on those points here:
1. : one API no matter what the application (SSE, WS, HTTP, Kafka, whatever) etc are all easily represented as Reactive Stream types. This greatly simplifies integration and composition of disparate services and data
2. Reactive APIs give me declarative, concise, deterministic ways to express complex, multithreaded algorithms. Remember: only one person TRULY understands how to write safe, concise multithreaded Java code... and it’s NOT you! Let the abstraction do the work
3. Robustness: reactive libraries give us a protocol to signal that our consumer is overwhelmed, or that it can not handle anymore. Libraries like @RxJava and @ProjectReactor provide operators to consistently handle errors, back-pressure, and more. safer code, in fewer lines
4. If container infrastructure is about being a better bin packer for infrastructure, reactive is about being a better bin packer for IO, threads, etc. it gives us a way to efficiently schedule work, cramming more scale into existing compute resources. An ideal pair for the cloud
