r/learnjava • u/[deleted] • Jan 05 '21
Whats the difference between Java, Java EE and Java SE ?
I know I can google it but the results are very complex, im just learning Java and I just looked at the job market and i found a job who wanted u to know Java, Java EE , Java SW and Java SE. Can someone explain it simply ?
3
u/2Bits4Byte Jan 05 '21
Do companies use java EE?
We just use jdk8 and spring webflux
3
Jan 05 '21
Yeah I saw a lot of offers wanting you to know EE
1
u/BikingSquirrel Jan 09 '21
Well, it may also be pure laziness to update that 😇 (or confusion what the latest term is)
But I may also be too far on the bright side ignoring the existence of good old EE projects.
As others stated, the concepts and even some of the APIs overlap with Spring Boot and newer stuff like Quarkus so you may want to read about those concepts and then choose one of the frameworks to play with them.
2
u/HecknChonker Jan 06 '21
Some companies definitely use JavaEE, but Spring is wildly more popular currently.
https://www.jrebel.com/blog/2020-java-technology-report#application-server
2
u/nutrecht Jan 07 '21 edited Jan 07 '21
Java and Java SE are basically synonymous and I would not worry about the distinction at all. "Java SW" isn't a thing, the W is right next to the E so someone just mistyped.
If it comes to finding a job; learn Java well, and build stuff using Spring Boot. That gives you everything you need to cover the requirements listed.
It's confusing because while "Java SE" is just "Java", Java EE isn't really anything other than a specification. So to be able to 'do' Java EE, you need to use a framework that implements it. Turns out, it doesn't work like that at all and you still end up vendor-locked to a Java EE implementation.
So most projects over time just switched to Spring. Spring is a partial Java EE implementation with a lot of other convenience stuff. As for Java EE; it doesn't exist anymore (it's Jakarta EE now) so you know that when a vacancy explicitly asks for only Java EE experience you're probably going to deal with old stuff ;)
In addition; you're getting a TON of replies here from people who are plain wrong, or at least have really outdated information. /u/HecknChonker is the only exception.
1
Jan 07 '21
Thanks! So Spring is like a very big library with things that help you with back-end of websites ?
1
u/nutrecht Jan 07 '21
Pretty much a big collection of big libraries :)
1
1
u/BikingSquirrel Jan 09 '21
Don't forget the tons of glue to hold them together preventing the whole thing to blow up 😁 Or all the nice things to make your life easier 🤞
11
u/knoam Jan 06 '21
Java SE is the language.
Java EE is technically called Jakarta EE now that it's spun off from Oracle. There's also Eclipse Microprofile which is similar but kind of a reboot/minimalistic fork of Java EE designed for microservices. Jakarta EE is a standard for a framework. So you can compare Jakarta EE to Spring in that it provides the same set of functionality: a web framework, dependency injection and some other stuff. Except when you write code for Jakarta EE you're coding against a standardized API. And when you run your code you get to pick an implementation, like WildFly or GlassFish or Payara or TomEE. The idea of having these different implementations is "coopetition". That is cooperation+competition. The different implementation vendors cooperate to agree on the standards and then compete to build their own implementations.
The standard+implementation part is a neat idea for a big company that doesn't want to get tied to a single vendor the way people are tied to Pivotal for Spring. But Spring is open source so if anything bad happened it would just get forked.
Java EE got a bad rap because it had some ideas that are now considered kind of obsolete. That was basically leapfrogged by Spring. But now Jakarta EE has evolved and in some ways is kind of newer and hotter than Spring, although its reputation hasn't caught up. CDI 2.0 is powerful and the other APIs have been tweaked to center around it.
I tend to be overly optimistic about new tech because I assume they learned all the lessons of their predecessors and then improved upon them. So I'm keen on Jakarta EE and Microprofile. But if you're more conservative and want to go with what's popular, that's Spring, specifically Spring Boot.
3
u/HecknChonker Jan 06 '21
I worked with EJBs and some other JavaEE stuff back when it was new and it was an absolutely terrible experience as a developer. I've heard the newer stuff is better, but most shops jumped ship to Spring a long time ago and I don't see them coming back.
2
u/nutrecht Jan 07 '21
They're not. The people who claim Java EE in it's newest incarnations is "hot" are the people who want it to be (because you know, certifications).
The last 10 years I've done literally one Java EE project, everything else was Spring. Sure there's a bias (I'm Dutch), but looking even at large conferences no one is really talking about Jakarta EE and Microprofile other than "oh, well that's cute I guess". They lost that race a long time ago.
It's a bit like C# devs who still claim C# is going to 'kill' Java 'anytime now'. :)
2
10
u/__rost__ Jan 05 '21
• JDK vs JRE: correct, plus the JDK has extra tools that are useful when developing - keytool, VisualVM, JConsole etc
• Not that well-versed in EE, so anybody with more experience please correct me: EE is targeted to servers in an enterprise ecosystem, with databases, messaging busses, cross-service transactions, etc. Keep in mind that all EE APIs can be used with some effort from within an SE environment, so it's a spectrum.
• EE is a specification; implementations of that specification may or may not need special licencing.
• ME is on its deathbed, please do not create new applications with it; it's a pre-smartphone environment for java apps (Sun/Oracle has a nice income stream from this before Android came out).
• No, there's the JRE and the JDK (which contains a JRE). EE is an environment, a specification on what extra APIs are available to your application code.
• What do you mean by server application? A plain JAR just needs the JRE. A WAR can run in a servlet container (tomcat/jetty). An EAR needs an JEE Application Server.
• ME is dead. Embedded system in this case means f.e. a featurephone with J2ME.
• JavaFX is extra classes that you can code agains (it's an API with an implementation).
• Most Linux distros will have either an official package or a way for the package manager to handle the installation.
• Applets are dead. As Oracle firmly believes it's the Only Company In The World, it won't point to the above-mentioned packages...
Formatting can suck my
2
u/rank_guru Jan 06 '21
Java EE - Java Enterprise Edition, This is basically the web edition in java. This is the most popular edition in Java. There are many popular frameworks developed on top of Java EE (Spring, Struts)
Java SE - Standard Edition, This includes base java this allows user to use databases, GUIs etc. We could develop desktop applications using java SE based components like Swing.
Both Java EE and Java SE depends on JAVA, So basically Java is the language we are using inside both Java EE and SE, Additionally now we got Kotlin and Groovy which is another JVM based languages which we could use instead of Java.
1
1
1
1
1
-2
u/its_kiran Jan 05 '21
RemindMe! 2 days
2
u/RemindMeBot Jan 05 '21
There is a 1 hour delay fetching comments.
I will be messaging you in 2 days on 2021-01-07 19:58:28 UTC to remind you of this link
CLICK THIS LINK to send a PM to also be reminded and to reduce spam.
Parent commenter can delete this message to hide from others.
Info Custom Your Reminders Feedback
0
Jan 06 '21
[deleted]
2
u/HecknChonker Jan 06 '21
Spring and JavaEE are generally considered competitors. You do not have to use JavaEE to build large scalable java services at all if you don't want to.
0
15
29
u/random_guy86 Jan 05 '21
Java standard edition (SE) is mainly used to build desktop applications. This has all the basic libraries and packages from simple type wrapper classes to GUI, networking, etc.
Java enterprise edition (EE) is used for developing web applications and scalable server applications.