Jakarta EE is officially out

Jakarta EE

Jakarta EE is officially out! OK, given the amount of publicity and evangelizing we and others have done around EE4J and Jakarta EE over the past few months you would be forgiven for thinking it was already the case but it wasn’t… until today!

I cannot stress enough how important this is to our industry. The number of Java developers globally is estimated at over 14 million. The Java EE market is estimated at a high multi-billion Dollar value to the industry. Yes there are other languages out there and other frameworks but none of them have yet made the impact Java and Java EE has over the years. Of course Java EE was not perfect for a variety of reasons, but if you consider how much of an impact it has had on the industry given known and debated limitations, just imagine how much it can bring in the years ahead if it were improved.

With the release of Jakarta EE we all have a chance to collaborate and build on the good things it inherits, whilst at the same time working to evolve those pieces that are no longer relevant or perhaps never were quite what was needed. Working within the open processes of the Eclipse Foundation vendors, Java communities, individuals etc., are all able to interact as peers with no one vendor holding a higher role than another. We’ve seen this exact same process work extremely well in a relatively short period of time with Eclipse MicroProfile, and I believe Jakarta EE can do at least as well.

When talking about Java EE and now Jakarta EE, some often focus only on the technologies. Fortunately those of us who have been in the open source world long enough appreciate that the community is just as important. With Jakarta EE, all of us involved in working towards the release hope that we can use it as a catalyst to bring together often-disparate Java communities under a single banner. Too often Java EE has been a divisive topic for some vendors and some communities, resulting in fractures and often working on the same problems but pulling in different directions. If Jakarta EE does only one thing, and that is bringing everyone together to collaborate, then I would still deem it a success!

I’ll finish by discussing why Red Hat has been helping to lead this effort along with others. I can summarize this pretty easily: enterprise Java remains critical to our customers and communities and we believe that despite the explosion of other languages and frameworks it should remain so for many years to come. Red Hat, and JBoss before it, have contributed to J2EE, Java EE and Eclipse MicroProfile for years and we believe that sharing our experiences and working on open source implementations is important for the industry as a whole, no matter what language you may be using. We believe it’s important to leverage Jakarta EE in the cloud and to a wider range of communities than in the past. We’re here to stay and will continue to help lead!

Finally, I’d like congratulate Red Hat’s own James Cobb. James’ design won the contest for the new Jakarta EE logo.

Onward!


To learn more, join these upcoming live sessions with Mark Little, Vice president, Software Engineering at Red Hat:

Join the Red Hat Developer Program (it’s free) and get access to related cheat sheets, books, and product downloads.

Share