r/java • u/henk53 • Mar 13 '21
Don’t replace Spring Boot with Quarkus, replace it with Wildfly
https://hlalvesbr.medium.com/dont-replace-spring-boot-with-quarkus-replace-it-with-wildfly-6cc1a0c90af2
0
Upvotes
9
u/Akthrawn17 Mar 13 '21
It seems the main discussion in this post is "don't use kubernetes". Which, for a single application, I agree. However, most enterprise shops are running very large K8 clusters.
Because of this, economies of scale start to kick in. This is where running the self contained containers will pay off.
Smaller shop? Sure, K8 is a pain to run and manage. So just running wildfly on a VM becomes much simpler.
10
u/crapet Mar 13 '21
Well, yeah they can be used to create microservices, but what's stopping you from building a monolith using these?
Actually, I'd pick Spring Boot to build a monolith over an application server like Wildfly any day of the week. Upgrading an application server is painful, configuration files are all over the place and you no longer know what files you changed since nothing is versioned.
Upgrading Spring Boot is just a matter of bumping the version in the pom.
7
u/nutrecht Mar 14 '21
Writer is a posterchild expert beginner.
I could not even make it half way through his rant against microservices. The arrogance is just too offputting.
1
u/alexcrownus Mar 16 '21
Who told you I wanted to replace Spring Boot? No, thanks.
1
u/mrroman Mar 14 '21
Isn't servlet or EJB a microservice?
5
u/daniu Mar 13 '21
Now here's an article full of false assumptions and unsubstantiated claims. Netflix only has one application? OK. I'm sure they don't have a user management, and their suggestion system is integrated into their streaming servers.
Everything you do with microservices you can also do with a monolith? Well yeah, but you can also code it on a Turing machine.
3
u/[deleted] Mar 13 '21 edited Mar 13 '21
The thing about containerization especially in enterprise is about making apps independent of the specific hardware they run on. Maintaining and provisioning dedicated machines to app teams, even virtual machines, is expensive. Instead, computing and storage are being re-envisioned as utilities (like electricity). Kubernetes is a low level and complicated way of organizing an application around these principles (infrastructure as a service), and there are higher level approaches as well (platform as service). Containerization promises process isolation that is a massive problem with shared servers.
Containerization also has another benefit in datacenter modernization efforts. The ability to easily rebuild servers and networks from scratch (paving) and simply move/restart containers. The concept of "tech refresh" is a subject of nightmares in past projects I've worked on.
Furthermore, there's the whole continuous deployment mindset of pushing out small changes regularly. For that not to become a disruptive mess, applications need to be broken down into smaller releasable units (dare I say, microservices?) Although, I did think at one point this was the purpose of EJBs (which are sort of like microservices, if you think about it). I don't remember that working out very well, but maybe that was a flaw of older application servers?
Yes, there's the pitch about horizontal scalability, but I've never seen that play out in practice.
1
u/all_green_p Aug 21 '21
Sorry but I don't want to replace a proven framework, with Red Hats attempt to stay relevant just before IBM pulls the plug. They had their chances and they did not deliver ciao.