r/javahelp • • Sep 15 '19

Is Java EE in demand?

Hello, as a junior, I'm interested with Spring, Microservices, REST, Docker, AWS etc. HR of a company contacted me about Java Developer position but it's based on Java EE, Oracle & MSSQL. As far as I know, Java EE is a bit legacy (and is an alternative to Spring) and used by banks and other fintech companies. I want to be relevant and keep my skills up to date throughout my career. Though, I want to know your point of view on this. Is Java EE in demand and will it remain so for the next 20-30 years? (I know it's hard to predict such things in tech industry but it may worth predicting trends)

Thanks!

33 Upvotes

34 comments sorted by

View all comments

5

u/__helix__ Sep 15 '19

As a junior developer, the key thing is to build proficiency/mastery of the language itself. Some frameworks will restrict components of the language so it is worth knowing where those blind spots are.

Learning how to write secure, transnational, scalable code is something you will spend decades doing. The frameworks come and go. Occasionally things evolve. Patterns will emerge. (Hey, yet another CRUD/Reporting variant) Some days it will be a stupid amount of data, sometimes it is about how fast it can go, some days it will be about shifting from one framework to another, sometimes it is porting something over.

What you are working on today... really does not matter. Never stop learning.

2

u/thesuperiorblack Sep 15 '19

I know you're right. And some of the things you've mentioned I will understand with time. In my current job I use JSF and it's demotivating. Compared to JS especially. As I have just commented out in another response, I want my skills to be in demand throughout my career. So I avoid if a tech stack feels like a dead end. For eg PHP. It's still used but why would I go for that direction? With your experience, how would you think about a job when the tech stack is a bit legacy? We can consider MSSQL too, as I've pointed out in OP.

2

u/__helix__ Sep 15 '19

Relational databases have been around for a long time - and one of the reasons they continue to be around is they do a damn nice job with some of the more common set of business problems. We have a mix of MySQL, Tiger (graph db), MarkLogic, Elastic (document db), Cassandra (key-value db), HBase (column db) front ending about 64 Springboot based REST services. Right tool for the right job.

Some tech stacks are a dead end or are not highly valued. I'm always evaluating what is going to be valuable. (Nothing quite like a few days on a deer stand to think about where things are at) It is funny - been slinging Java since the .9 days, so always looking to say 'what is next'. New shiny always becomes old busted.

Doing a bit of Java EE and relational is not going to hurt anything. When I'm interviewing, there is slim chances anyone has actually worked with most of the NoSQL databases or frameworks we use. I've done the Java EE, JSF (and even ADF for that matter) and will dig to see if you developed competence/mastery with the tools you worked with and how effective you were with the tooling you had. Java EE stuff you are currently doing is still within that Java wheelhouse.