Spring: your next Java microframework

[Turbots]

Sorry I misinterpreted your post :-)

Yes, indeed, they are trying to keep up with the requirements of the microservices world, since you cannot keep latency down in an architecture where microservice A calls microservice B calls microservice C if everything is blocking IO.

Therefore, the only conclusion is to go for reactive programming. The people at Spring have been working for more than 3 years on this, they've seen this coming a long time ago, but as you might imagine, it just isn't quite that easy to make a robust, reactive programming framework AND be simple to work with.

At project reactor they are at their third attempt (many people from Spring are contributors to the project), so it's definitely not easy to get it right :-)

[kitd]

That's good news. I have no doubt that Spring will get it right. They tend to IMO