I don't know how you would build architectures today without reactive programming. Once you've gone reactive, it's super hard to go back, because - deep down - you know you can deliver more performant, robust, resilient, scalable software with reactive. Why would you do otherwise? I love reactive programming, because it makes writing production-worthy software easier and faster. In this book, Reactive Spring, I'll show you why by introducing the wide world of reactive Spring.
Follow @ReactiveSpring on Twitter for more


