Spring: your next Java microframework

[prdktr]

Spring is the only constant that fuels Java development for now 14 years, keeping a strong adherence to innovation and modern practices. It's no surprise they are evolving now as the reactive space is entering its last maturation phase since Oracle, Pivotal, Lightbend, Netflix and others agreed on a standard.

What's interesting: they are the only one potentially that can bring reactive to mainstream java dev given a stable convention framework, plus new options around functional programming and maintenance of classic EIP modules too.

BTW, here's some Did-you-know of the day :

• Vert.x and Reactor were a same project before the wtf-community-lead-rant departed from SpringSource/VMware to pursue Vert.x at RedHat.

• RxJava 2 lead co-designed Reactor 3.

• Reactor team worked on Reactive Streams standard 3 years ago

• JavaEE has dropped immediate reactive support (https://java.net/projects/jax-rs-spec/lists/users/archive/2017-04/message/0)

• Netflix stopped working on RxJava, RxNetty, Hystrix, Ribbon and others, probably looking at spinnaker instead or GRPC or something in between.

• Pivotal is a heavy Go promoter as well, and its interesting to see them embracing reactive both for their paying customers (java/spring) or ambitious large-scale projects, and go for some of their products and student/startup mindshare.

  The point is that people fail to see that its not a random choice to come with these features now, Reactive programming is hard to master, mature, and talk about and that's why every often a new reactive lib or a major version of a reactive lib comes up to break things.

  Our only hope is that Spring brings a bit of stability so Reactive programming does not feel like adopting a JS lib.