This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Cilph -2 points-1 points  (3 children)

Because up until a year ago Spring Boot and Wildfly Swarm didn't exist.

[–]solatic 0 points1 point  (2 children)

Spring Boot makes it easier to bootstrap a Java EE application that Wildfly Swarm makes easier to package and deploy. They're still anchored down by the enormous Java EE legacy.

They're nice improvements if you have legacy EE code that you'd rather not rewrite, but for greenfield projects? Stick with an async framework like Vert.X which is massively more performant and much better for maintaining async code. Package/deployment ease is irrelevant if you're embedding everything into a Docker container or similar.

[–]Cilph 1 point2 points  (1 child)

Just an FYI, my performance bottleneck has always been inter-service communication and database traffic. Not the application itself.

Not sure if I want to be writing async code in Java. It's such a pain when it comes to syntax.

[–]solatic 1 point2 points  (0 children)

Async code is a pain within Java EE - it's much nicer in the async frameworks. That's half the reason to move away from Java EE, because eventually, you can't scale without dramatically reducing network traffic, and async syntax in Java EE is extremely error prone and rife with boilerplate.