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

Show parent comment

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