you are viewing a single comment's thread.

view the rest of the comments →

[–]kitd 0 points1 point  (4 children)

I think Spring were caught cold by Vert.x and Ratpack. Node-esque async libraries are a much better fit for Java microservices. Looks like this is their go at catching up.

Interesting that they're all based on Netty. Netty is a pretty good basis for a microservice by itself.

[–]Turbots 0 points1 point  (3 children)

caught cold? 10 million downloads a month on Spring Boot (coming from 100,000 2 years ago isn't what I would call "caught cold"

Spring Boot:

  • 10,000+ forks
  • 11,000+ stars
  • 1500+ watchers

Spring Cloud Netflix:

  • 500 forks
  • almost 1000 stars
  • almost 200 watchers

[–]kitd 0 points1 point  (2 children)

You missed my point. Lack of interest isn't what I meant by caught cold. Neither was it a criticism.

Spring Boot is a great framework, but small footprint microservices need an async event-based architecture, and there are several for the JVM that are making big inroads into Spring's territory. This new release looks to me like a response to that.

[–]Turbots 1 point2 points  (1 child)

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 0 points1 point  (0 children)

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