loading...

Java EE is dead, why still using it?

omarmuhtaseb profile image Omar Muhtaseb ・1 min read

I've been working as a software developer for 3 years now. In those years, I worked with Java as the main web development language, primarily Spring Boot framework within micro-services architecture.

I know that I barely have experience in the web development, but I still see some companies seek Java EE developers while they're adopting the micro-services architecture. I mean why would you do that! Do we need Java EE in the micro-services architecture? Should I know more about Java EE Servlets and Pages? and most importantly Is Java EE dead especially with all the hype of micro-services?

What do you think folks?

Discussion

markdown guide
 

IMHO, it's far from dead, but it's losing ground for sure.

The JavaEE specification and APIs can eliminate the need for maintaining Maven dependencies, which can be a security liability if you don't know how to avoid insecure JARs from being compiled into your web application. Imagine building a robust web app using only the standard library of your programming language of choice so you don't need external dependencies (or very few): that's the use case JavaEE is best intended for.

The Eclipse MicroProfile specification within JavaEE is an attempt at giving JavaEE a second wind as well, given the popularity of microservice architectures.

 

Thank you, this is the very first time that I hear about Eclipse MicroProfile.