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

3

u/QuicK1024_tv Sep 15 '19

Java EE is in demand for companies which are not migrating to newer technologies. Taking a position as a Java EE developer is not a bad thing, and you will learn a lot, but will either be a comparatively temporary position or the company will migrate to newer and better technologies.

1

u/thesuperiorblack Sep 15 '19

I'm curious about all the comments but the responses made it a big foggy too. As I have mentioned in the OP, JRE is a bit old, seems like. I did not claim it's not in demand but help me with this conclusion. I want my skills to be in demand throughout my career so tech stack is one of the most important aspects when I consider a job offer. If my goal is this, should not I be attracted to Spring and avoid from Java EE, is not that a straightforward conclusion?

3

u/QuicK1024_tv Sep 15 '19

It really depends what path you would like to go down. If you purely want to stick with a Java backend, Java EE or Spring will both give you in-demand skills and to be honest I don't know what the future of those two technologies will be. As someone else said, Java EE seems to be moving more than it has in the past with Oracle and could even become the standard over Spring.

If you want to focus on newer technologies like restful backends, microservice architecture, AWS or similar services, then I would stay away from both spring and Java EE.

All of that said, a first job is a first job and having one will be extremely valuable to your career rather than waiting two years to get the one you want. Having any experience where you have touched data storage technologies, worked with a team to fix code and produce new features for a product, used some kind of version control, had some front end or back-end experience, etc will be the most beneficial thing for your career. All of these combined will give you enough experience to talk intelligently about the full stack of an application and that will be enough to get you in the door of most companies regardless of what technologies they are using. (If you can get past HR)

That is, unless you're a 4.0 student with 2 years of internship experience who will have his pick of job with any company. In that case, going with the latest and greatest can land you a paycheck sometimes 2 or 3 times higher than average (after at least 5 years). My uncle works for a data solutions company and said he was hiring seasoned AWS developers for 300k plus a year (that was about 4 years ago), to give you an idea of what I mean.

In regards to your comment "tech stack is one of the most important aspects when I consider a job offer" I wouldn't let this lay too heavily on your opinion. For example, when I started with my current company, they were still using ant, struts, and jboss to deploy a Java web app. Now, we are moving to a microservices architecture with containerization, restful backend and an angular 8 front end. (Yes I know restful services are already becoming outdated but that just shows how little the tech stack actually matters). In my opinion, the most important consideration is if your company is willing to invest the resources to update it's applications tech stack and keep the code clean, organized, maintainable, and expandable. The tech stack should never be concrete.

I hope this helps!

2

u/thesuperiorblack Sep 15 '19 edited Sep 16 '19

It's a great answer and a wow for that AWS developers. I would like to understand why you said that I should avoid both if I want to use "newer technologies like restful backends, microservice architecture, AWS or similar services". Aren't they working integrated already?

Also, I was not that aware RESTful is becoming outdated. The big picture I know (so far) is something like this: Microservices deployed on AWS in Docker containers, sending each other requests in REST fashion with the help of Kafka/RabbitMQ.

As you've said, I want to learn stuff quickly and gain deep knowledge on the language, software development and in tech stacks. I regularly check out job posts since 1,5-2 years and the tech stack we've been talking about can be the most demanded one (for backend). So when they put some senior job they prefer 5 years Spring, 3 years AWS for example and if it's possible to start using them today I'd like to go that way. I definitely see your point though, I should maybe mention that I am planning to relocate to EU when I get enough experience so I'd prefer a job with latest tech stack.

Lastly, I value tech stack more than salary. I have friends who got 25% more starting salary than the others but they work for defense industry, using very low level coding and very old tech. The seniors of there told them they'll have significant hard time if they'll look another company after there because their skills won't be in demand as others. This is why I might put a red flag when I see an old tech.

Looking forward for your thoughts :)

3

u/QuicK1024_tv Sep 16 '19

I mentioned that you should avoid both because like was said by dharma_analyst, its almost an entirely different tech stack, so you don't need a Java back-end at all.

I also replied to him about why REST is "becoming outdated" considered the lesser of two great API design architectures.

I'm not sure I can say too much more that hasn't been said by other contributors here except to say that yes, you are right: putting the tech stack first will allow you to rise above and stay a top competitor in the market but may give you a lower starting salary.

The reason companies are dishing out high salaries for vanilla JS, AngularJS, Struts 1, etc. is because at this point, those things have become specializations rather than in-demand, expected job skills. So, just like those are specializations, there are also new tech stack specializations (such as the AWS developer mentioned above) that can result in high salaries.

So, to sum everything up...it doesn't really matter. Just do what makes you happy because that is the #1 thing that will keep you going and keep you motivated to keep bettering yourself and your career. At the end of it all, that is what will take you above other developers.

2

u/dharma_analyst Sep 15 '19

I agree with what was said. When you build micro-services architecture the goal is to create simple and lightweight components. For that reason you will usually pick micro-framework like Dropwizard and add some other libraries only when you need it for a specific purpose. You usually don't want to start with huge framework. Not even DI container is required. You just create and wired all of the app dependencies on one place and that's it. I can tell you that from my experience working on such architecture is much more enjoyable, because things just work and you feel pretty productive. No hidden magic, no complicated bloatwares, just KISS.

The other side is that this usually works in smaller companies and startups when things need to move quickly and effectively. My friends working in large companies don't have these opportunities, because their companies use software built using older technologies in monolitic architecture and it takes ages to move to something more modern. Therefore there will be less job offers allowing you to work with trendy stuff and money might not be so great sometimes. However if you achieve to get such job it can be pretty rewarding.

Regarding REST I'm not quite sure what author meant. Never heard of it being outdated. Although different RPC methods like gRPC are being more popular for inter-service communication.

Btw. if you don't know ThoughtWorks Radar it can be something of your interest.

1

u/thesuperiorblack Sep 16 '19

That's a wholesome answer thanks :) I just wonder what you meant by saying "if you achieve to get such a job it can be pretty rewarding". Working with new and promising tech stack is great obviously. But does it also compensate the salary in the long run? So putting tech stack first, money second will eventually mean your salary will be great too? (except you may get lower salary "sometimes", as you pointed out)

2

u/dharma_analyst Sep 16 '19

I mean in a sense like personally satisfying. For me this is more important than salary package. I work in a very small startup company having maximum freedom. I would never sacrifice this position for let's say position in a bank just for getting more money. Especially after my previous working experiences. It can take time to find a job with such great conditions and sometimes it requires to get some experience in not so great companies first and work hard to become skilled so you can get your dream job later easily, but it's worth to follow this path.

1

u/thesuperiorblack Sep 16 '19

Got it and congratulations for finding where you are happy at. Can we, broadly speaking, say that the more company is old & big its harder to change the tech stack quickly but the salaries are higher, and vice versa. Do you come across exceptions to that?

1

u/QuicK1024_tv Sep 16 '19

I suppose I should have chosen my words more carefully. Companies that are literally using the latest and greatest are moving past REST now. Check out this article from an AWS employee for an interesting read on what may come after REST. GraphQL seems to be what people are migrating towards.

Here is an article comparing REST and GraphQL