My personal favorite is <a href="https://vertx.io" rel="nofollow">https://vertx.io</a> because it is a little more transparent in how it works and the Rx abstractions are something I was familiar with when I started using it. Not to mention springboot did not offer reactive programming until fairly recently whereas vertx has been reactive from day 1, rxjava or not.<p>I will take another look at springboot just to see what the fuss is about. I am a bit surprised that netflix did not come up with their own light weight backend framework based on netty.
As a developer that worked mostly for companies that really like to build stuff in-house, it was my understanding that startups build on top of frameworks to be scrappy / create the most value per hour of work, and large businesses create their own frameworks / tooling, mainly because they have very specific needs.<p>Is my understanding wrong? Or, maybe this is mostly a PR thing?<p>PS: They do mention that they used to make in-house tooling, but then why transition? How is depending on a codebase that you have less control over an option when you have Netflix resources?
Spring Boot has been the de-facto standard standard in the industry for years. Java newbs even associate it with Java Backend. There's nothing else.
If I'm a developer whose primary expertise is in Node with a smattering of Laravel and Rails, what should I be expecting if I decide to write an api with Spring Boot and Java? I've been curious for a while (Java performs very well on most benchmarks, and it looks great on a resume), and I've identified Spring Boot and Vertx as the two main web frameworks in Javaland.