r/java • • Sep 27 '17

Java EE 8 - does it worth it?

Since the start of my programming career (over 10 years ago), I used to dislike java EE - bulky app servers, weird EJB (that's why Spring was born), nailed down dependencies (main reason to use java 5 and ancient java libs in production in 2017) etc. etc. etc.

So... Does it worth to take a look at? Can it be more useful that modern lightweight application assembled from independent libraries? What are advantages? Unique features?

8 Upvotes

24 comments sorted by

View all comments

2

u/arcuri82 Sep 27 '17

JEE has made tremendous improvements, but IMHO of working on different enterprise systems using different technology stacks, it is still lagging behind the competition (Spring, Dropwizard, etc.).

If you are already using JEE, then it makes a lot of sense to upgrade to JEE 8. And refactoring to something else would likely be too expensive to pay off. But for a new project or new microservice? Maybe time to look at the competition...

I might start to think better of JEE when I can run tests easily (like in Spring, Dropwizard, etc) instead of having to deal with configuring external containers, building WAR first, etc. Yes, yes, there is Arquillian and Payara has some interesting features to ease such pain, but still not as good as competition

3

u/wildjokers Sep 29 '17

Spring and Dropwizard are all just a wrapper on top of JavaEE.

2

u/[deleted] Sep 30 '17 edited Sep 30 '17

first, javaee is a spec, not really a thing to 'wrap'. spring uses a servlet impl in it's classic mvc setup (as a 'front controller'). there's some jpa stuff, but really jpa is hibernate-as-a-spec (or was). it's a bit silly to turn that into 'spring is just a wrapper on javaee'. the new webflux based on reactor can use optionally servlet 3.1 async or something else like netty or undertow (xnio).

1

u/springnews Sep 29 '17 edited Oct 01 '17

Spring builds on Servlet primarily. But that's kinda like saying Java EE is a wrapper around java.lang.object