Imagine a bacon-wrapped Ferrari. Still not better than our free technical reports.

10 Kick-Ass Technologies Modern Developers Love

Tomcat and TomEE

First Release: 1999
Latest Release: 8.0.9
Interesting Facts: Tomcat was originally a merger of Sun Java Web Server code and ASF RI if Servlet 2.2 and JSP 1.1, hence starting at v 3.0.x

First Release: April 2012
Latest Release:
Interesting Facts: TomEE is certified for Java EE 6 web profile and aimed at Java EE 7 full profile.

10 kickass tools developers love tomcat and tomee

10 kickass tools developers love app server

Tomcat is the leading free, open-source Java Application server people turn to when writing Java Web Applications requiring JSP and Servlet support. TomEE provides Java EE support to the existing Tomcat base, retaining the Tomcat look and feel. Neither Tomcat nor TomEE require a litter box.

With Tomcat in use by an even 50% of developers surveyed, there is no doubt as to which application server is the first one people think of when it comes to Java development. TomEE, an extended profile for enterprise developers that even partially supports Java EE7, is now professionally supported by creator David Blevins’ company Tomitribe. Both Tomcat and TomEE are geeks’ choices because their popularity and high usage by development-only teams, where production servers are not considered.

Tomcat, long the indie developer’s hero, is now used extensively in enterprises, namely when development teams get to choose their own app servers. This is where TomEE comes in: as the natural extension of Tomcat into Java EE, TomEE combines the huge community of Tomcat with the attention to enterprise needs.

Source: Java Tools & Technologies Landscape for 2014

I think one factor for our success is our religious adherence to all things Tomcat. TomEE is the Java EE version of Tomcat, the most popular Java app server out there, and it’s supported by all tools that support Tomcat, whether those tools know it or not. While TomEE works out-of-the-box with Tomcat tools, many have added support that takes advantage of the extra features TomEE brings. JRebel was actually the first back in 2012, and Intellij, Jelastic and most recently NetBeans are proud supporters.These days what our users want most for TomEE is Java EE 7 support, and many of the Apache projects we need for Java EE 7 are nearing completion. Although the core of TomEE is very good and always getting tighter, I’d like to see improvement is in the professional dressing around the project. Many people have praised the documentation, but I still see room for improvement, and more frequent releases is also quite high on my list. We’ve also done two security releases in the last quarter, each timed right behind the respective Tomcat security releases. We need to keep that up.
– DAVID BLEVINS, Creator of TomEE


  • theschmitzer

    Hard to believe Jenkins makes the list. Does not scale to even a moderate number of builds.

  • Actually Jenkins is not that bad. I just pulled the stats, we have 878 jobs configured (a lot of duplication because of handling multiple branches), 25 servers in the cluster and about ~200 executors. It gives us builds and tests on ~4 different platforms.

    I think Jenkins does scale but it requires work in administration and monitoring.

  • Sunil Giri

    Still like Eclipse & Maven over IntelliJ & Gradle, may be not modern enough !

  • Why do you prefer Eclipse over IntelliJ? I switched to IntelliJ in 2006 and never looked back. Here’s why I prefer it:

  • Sunil Giri

    Thanks for responding, I started using Eclipse in 2004, never felt a need to change untill I landed on a multi module JSF, Maven project in 2007 which used MDA , Eclipse started consuming lot of memory and became very slow, I tried IntelliJ back then,but IntelliJ also had similar memory requirements, I dint like the look and feel, may be since it was different from eclipse, also I was not sure if the learning curve (from workspace->project of eclipse to Intellij modules structure to other details) were really worth, Eclipse was free and IntelliJ community edition. But I like what you have written about IntelliJ’s front end languages support, so plan to give it another look.

  • Satheesh Ak

    Top 10 Technologies –

  • An0nym0usC0ward

    I, for one, have to use Idea at work. But I still don’t like it. People say it’s more convenient than Eclipse in many ways, but I find it gets in the way and annoys me in many ways.

    For example, its refactorings are hidden too deep, and I don’t need it to do a deep rename often enough to justify its smarter rename. OTOH, I do want to Ctrl-Left/Right through just parts of camel-case identifiers very often, which it doesn’t know, it seems – even most plain text editors do this, but not Idea. Its version control interface is streamlined, but not nearly has powerful as I’d like it, which is why I use an external tool anyway, with both Eclipse and Idea. I absolutely dislike Idea notifying you of errors only by red zig-zag underlines in the project explorer, instead of a Still, I do more of the SVN stuff in Eclipse than in Idea. I could go on for quite a while, but I think it’s a matter of personal taste.

    Idea feels like a thin wrapper on top of external tools, rather than a full-blown IDE. While I do like the idea, I don’t necessarily like the implementation.

    Then again, I do use Linux as an IDE – – so my way of working on code might be somewhat particular.

  • An0nym0usC0ward

    Sort of mixed content. I definitely know a lot of programmers who profoundly dislike at least half of the enumerated technologies. Maybe it’s just a list of technologies who built a lot of hype around them recently? Hype doesn’t always correlate with lasting value.

  • Fernando

    Angularjs with all my heart. And Jrebel

  • Andy Gumbrecht

    Thank you so much Oliver an Simon. I hope it’s OK to plug the TomEE 1.7.0 release here,