| 2022 | Jun | May | Apr | Mar | Feb | Jan |
| 2021 | Dec | Nov |
Here are the choices in alphabetical order:
Picking a popular technology makes our developer life easier: Easier to learn, easier to build, debug & deploy, easier to hire, and easier to convince teammates & bosses. Now popularity can make a difference in two situations: When multiple technologies score the same, we could go for the most popular one. And when a technology is very unpopular, we may not use it.
I measure popularity among employers and developers as the trend between competing technologies. I count mentions in job ads at Indeed for employer popularity. For developer popularity, I use Google searches, Udemy course buyers, and Stack Overflow questions.
The Indeed job search is active in 62 countries representing 89% of the worldwide GDP in 2020. It demonstrates the willingness of organizations to pay for a technology - the strongest indicator of popularity in my mind. Jakarta EE is the baseline.
And here are the remaining frameworks compared against Jakarta EE. They don’t all fit into the same chart. Helidon and MicroProfile are missing because they are at or below 1%, compared to Jakarta EE.
Spring Boot wins, and Jakarta EE is second. Jakarta EE is losing ground against Spring Boot again. Dropwizard, Quarkus, and Micronaut are an order of magnitude behind Jakarta EE. Quarkus is back as number three, as Dropwizard mentions dropped like a stone in one month (couldn’t resist that pun): From 1,175 to 259 in one month, which is a loss of 78%.
Please see here for details, caveats, and adjustments of the job ad mentions.
You can find the detailed search results with links here. They include breakdowns by continents:
Udemy is one of the biggest online learning sites. They publish the number of courses and students (beyond a certain threshold). This shows how many people evaluate a technology. Jakarta EE is the baseline. The other frameworks haven’t crossed the reporting threshold for Udemy (probably around 100,000).
Spring Boot wins over Jakarta EE and is increasing its lead. But Jakarta EE had a strong month, forcing the slowest growth of Spring Boot since last November.
Here are the links that show the courses for all and the number of students for some:
Google Trends demonstrates the initial interest in a technology over time. Here are all frameworks, but Helidon - Google Trends only allows five at the same time:
This link produces the chart above. This version switches in Helidon for Micronaut, and this one MicroProfile - which isn’t making a difference in the chart.
Spring Boot wins, and Jakarta EE is second. Jakarta EE’s decline in popularity to 2% of its June 2004 popularity is just stunning. Spring Boot just hit its all-time high (a repeat of its July 2019 score). It’s 17 times as popular as Jakarta EE and 35 times as popular as Quarkus.
We can’t pick a third place in the chart, so let’s zoom in on the five challengers over the last two years:
This is the link for the chart.
Quarkus leads. Quarkus added 40% over the last two years while MicroProfile stayed flat. Micronaut and Helidon lost a quarter of their search volume, DropWizard lost two thirds.
How does Jakarta EE fare against Quarkus?
Here’s the link for this chart.
Jakarta EE lost 28% of its search volume, and Quarkus is inching closer.
Stack Overflow Trends shows which percentage of questions at Stack Overflow has a particular technology tag. It is a proxy for using a technology during evaluation and productive use. “More questions = better” to me.
This link produces the chart above.
Spring Boot wins by an order of magnitude, while Quarkus places second and Jakarta EE third. Spring Boot is nearing its mid-2020 peak again. Quarkus grows slowly but just reached its peak value. Jakarta EE hit rock bottom in 2022 and is increasing again. DropWizard, Helidon, Micronaut, and MicroProfile don’t have a tag on Stack Overflow.
javax.* to jakarta.*. So even though Jakarta EE saw three releases since 2019, I think relatively little functionality has changed since Java EE 8 in August 2017. But the more significant issue is that Jakarta EE was designed for application servers like IBM WebSphere that host many applications on big and expensive servers. We’re rapidly moving into a world where our Java applications run as close to the metal as possible, all by themselves as microservices in small containers or even serverless. This world has no place for application servers anymore. Will it have one for Jakarta EE? Only time will tell.So here’s my recommendation: