r/javahelp • u/thesuperiorblack • 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!
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.
8
u/maokei Sep 15 '19
Java EE is still in demand will remain for a long time, no only that java and Java EE have been a slow moving ecosystem for a while. That is changing quickly the jump from java 8 to 11 and 12 has been a quick one compared to java 6 to 8. And Java EE is a now a eclipse foundation project instead of being run by oracle that did not really seem to care much. To me it feels a lot like spring picked up the slack where oracle was doing nothing at all with Java EE.
3
u/thesuperiorblack Sep 15 '19
So what do you think moving to Java EE while using Spring etc before? Will Java EE be relevant regardless of the company size (large fintech or startup) now and in the future (compared to spring)?
4
u/MrSquicky Sep 15 '19
There are plenty of companies using Java EE and there will likely continue to be in the future, but Spring is much, much more prevalent right now and, barring some mjor shakeups, it will likely remain that way going forward.
Personally, if I were looking at a job that was Java EE and not Sprint (Boot), I'd want to know why, whereas Spring is the default.
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 :)
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.
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.
14
u/FrenchFigaro Software Engineer Sep 15 '19
Spring IS Java EE.
Java Enterprise Edition is not a framework, it's a platform specification within the Java language and set of tools implemented by various application servers (Weblogic, JBoss, Glassfish, Tomcat...) for web oriented application.
Spring is one of many frameworks built over Java EE.
14
u/nerdyhandle Sep 15 '19
Spring IS Java EE.
No.
Spring doesn't fallow the Java EE specification. It also doesn't contain a lot of EE functionality like EJBs for instance.
Java EE is more than just the Javax namespace.
10
u/snot3353 COMPUTERS!!! Sep 15 '19
To be a little more specific, this is true about Spring MVC and some other projects. Other Spring libraries and frameworks like Webflux are not built on top of JEE.
15
u/dharma_analyst Sep 15 '19
Spring framework doesn't implement Java EE specification and therefore is not consider as Java EE. The list of official implementations can be found here.
1
Sep 15 '19 edited Sep 15 '19
I use java EE with spring rest services in pretty much everything I build for a pretty big project for my job. It’s a common tech stack in my company. We’re a couple years behind the curve but to my understanding a lot of companies are even further behind us.
Edit: as for will it stay relevant that’s pretty unclear. Your job as a programmer is being a learner though. No matter where you go you will be expected to keep up with latest tech and understand the benefits and downsides to current and emerging tech stacks.
Always bet on java though. That’s not going to go away for some time. It’s undergone a lot of evolution and is really easy to develop in due to the crazy amount of packages you can utilize.
1
Nov 24 '19
Here in morocco JAVA EE still the most demanded programming language in the market like (80% of programming jobs)
-6
u/dharma_analyst Sep 15 '19
From my experience in London there is not big demand for Java EE and if you want to enjoy your job just avoid this technology. The concept of application servers was a bad idea and working with them is pain. There are some parts of this standard they are good though and you can use it standalone, like JPA for instance.
3
u/_cjj Sep 15 '19
Translation: I don't understand this thing; therefore, it's terrible
1
u/dharma_analyst Sep 15 '19
What about: I worked on several Java EE projects and found this technology unhelpful and counterproductive.
-1
u/thesuperiorblack Sep 15 '19
Thanks for the response. Yet, it's still unclear for me. On one side, it looks a bit legacy but on the other side it looks its already used widely used. I use JPA, JSF and Spring too but I feel Java EE based job will be legacy, without Spring and maybe with JSF and JSP. I feel like it'd be dead end path compared to working with latest tech stack.
-2
u/dharma_analyst Sep 15 '19
It's still being used, but I wouldn't say so widely that it'd limit your job opportunities drastically. You're right, it's a dead end path and thus better not loosing your time with it unless you have no other choice.
-1
u/thesuperiorblack Sep 15 '19
That's it. The answer I was looking for :) Thanks.
2
Sep 15 '19
But it's not the correct answer.
Java is Java. If you can work with Spring then you can work with Java EE, and vice-versa. I don't think it'd cost you in the long run to work with Java EE. And even if you did work in a Java EE shop, you could try push them towards Spring if you wanted.
Employers will hire on your ability to do the job, not on which specific technology you currently use (given everything you're talking about is Java).
I don't think it would adversely affect your career to work with Java EE.
I would consider the company itself. Is it a company you want to work for? Is it in an industry you are interested in? Does it offer opportunity for growth? Can you influence their tech stack?
You can integrate Spring with Java EE, you could try convince them to start using Spring for some services.
We mix a lot of different tech stacks at our place. As long as the services can communicate with each other we can use what we want.
0
Sep 15 '19
[deleted]
5
u/__helix__ Sep 15 '19
Isn't that the truth. I remember we discovered HR was /dev/nulling resumes that said EJB, because they were trying to hire J2EE resources. /headdesk.
4
u/AloticChoon Sep 16 '19
Most of time hr have no idea what they need.
It isn't just HR, Project Managers also have no clue sometimes....
I got a job in '98 where they explicitly stated they were looking for people with 10 years experience in Java.... yeah ok....
6
u/_cjj Sep 15 '19
Let's assume for a moment that Java EE is legacy and deprecated (it isn't, expect in name, but we'll get to that).
As a junior, a good chunk of what you'll learn will be from transference - you'll learn from experienced developers and experienced code. Sometimes you'll learn from the good stuff, and others you'll learn from bad code or mistakes.
Java EE isn't like Swing - it's better considered as an official way to implement a bunch of libraries and principles. If you learnt Java EE, you'll learn the same beans and injection stuff that makes other, similar, frameworks very easy to pick up.
Learning or working with JEE isn't a cul-de-sac career choice - I'm tempted to say that you might find the experience is more valuable than not having it.
Anyway, Jakarta EE is the official continuation of Java EE https://jakarta.ee/about/, so worth being aware of that if you have to talk about it at any point.