The current results in the 9th annual worldwide developer productivity report provide us insights into the present state of Java from 2021. More than 850 Java developers responded to queries regarding their experiences, favored tools and technology, and what difficulties they face.
Topics covered include the nature of Java teams, challenges that they encounter, favored tools, and achievement of said tools and technology. The important finding demonstrates that despite increasing utilization of microservices, developers are facing long redeploy occasions and interservice performance problems.
Java and microservices trends
The poll found 49 percent of respondents were Java developers, with the remainder split across staff contribute, architects, and consultants. It was great to hear that everybody who reacted is a the job, with just more than a third (36 percent ) within a venture (bigger ) organization, 42 percent in little or midsize businesses, and 15 percent in start-ups. The vast majority work in tiny teams, which can be indicative of a growing desire for more rapid adoption and development of microservices, in which developers work with smaller sections of code. 40 percent of groups are between 3-9 individuals, 24 percent 10-20, and 17 percent 20-50 people.
Java and microservices trends
Adoption of microservices remains stable, with 66 percent of respondents actively transitioning to or now using microservices. Just 13 percent of respondents aren’t likely to transition in any respect. developers were asked the number of microservices they had in their principal software, on a scale of 1 to 20. The replies were 36% with 5-10 and 34% with 1-5, followed by 16 percent with 20 or more and 14 percent with 10-20. Obviously, organizations may have more than 1 software structure, for example monolith remains employed by 42 percent, SOA by 29 percent, cellular by 23 percent, and background by 18 percent.
Most Popular Tools
The report surveyed respondents in their hottest tools and technologies in each class:
- Application servers – Tomcat still predominates at 66%. Then there’s a relatively even spread between JBoss/WildFly (19 percent ), WebLogic (18 percent ), Jetty (15 percent ), and WebSphere (14 percent ).
- Application framework – Spring Boot takes the best slot in 62%, a reduction from last year’s 83%. Consumers of DropWizard sit 8% (a rise from the 2020s 1 percent ); similarly, Quarkus adoption grew from 1 percent to 6%.
- Framework configuration – Annotations is the leader in 75%, whereas 22% configure with code inserted to methods that operate through initialization.
- IDEs – IntelliJ IDEA comes in at number one with 65 percent, followed closely by Eclipse (48 percent ), VSCode (27 percent ), and NetBeans (13 percent ).
- JRE/JDK distribution – Utilization of Oracle JDK traveled up — 59 percent compared to 50 percent last year — even though reports of people moving out from it because of licensing expenses. This might be due to the quantity of bigger enterprises who responded to the poll, as they frequently find the transition more difficult than smaller businesses. In 2nd place is AdoptOpenJDK in 22% plus a further 10% record with Amazon Corretto.
- Databases – The most favored is MySQL in 43%, then Oracle DB and PostreSQL sharing the second position in 36 percent each. Next up was MongoDB, with 29 percent of respondents.
- Build tools – Maven is your very best tool of choice in 67%, whereas this past year, Maven and Gradle proved pretty much neck-and-neck.
- Virtualisation tools – 88% say that they use these resources, together with far and away the most common one being Docker in 57 percent, down from 74 percent this past year. Kubernetes is the runner-up at 42%, a step up from 35 percent 12 weeks ago. VMWare sneaks in at third place with 27 percent (again, a rise in contrast to 2020).
- CI/CD – Jenkins stood with 61 percent of respondents using it, together with other people (Bamboo, TravisCI, TeamCity as well as many others ) in 12 percent or less.
- PaaS – Many respondents are currently using a PaaS supplier, with just 24% stating they don’t. For people who utilize a PaaS supplier, AWS has been the best choice at 39 percent. Microsoft Azure follows with 24 percent and Google Cloud with 18%.
Developer Pain Points and Challenges
The largest application performance problem cited was long program response times at 54 percent (which can be on a level with last year’s 55 percent ). This continuing tendency aligns with developing microservices adoption. The next greatest performance problems reported have been high CPU use (39 percent ), and memory leaks (35 percent ), together with excess open relations and IO inquiries coming in at 26% and 19 percent, respectively.
Deployment times really are a frequent region of grievance. There are two possible reasons supporting this. One is that if microservices increase in size, it takes more time to develop and make applications. The next reason is because of microservices running on distant virtualization machines.
In particular to microservices, troubleshooting inter-service performance has been the largest reported obstacle in 30%, followed by issues with establishing the growth environment locally (24 percent ). This is sometimes attributed to the issues of producing an intricate microservice program. In joint third place in 14% each would be the challenges of upgrading inter-service functionality difficulties and monitoring and scaling in manufacturing.
In the end, developers were asked how they’d spend additional time throughout the workday if their challenges are mitigated. A quarter of respondents stated they’d concentrate on improving test coverage, followed closely by enhancing program performance (21 percent ). 19% say they’d add new attributes and 15% will spend those additional minutes enhancing the development procedure.
12% would accelerate their launch cadence, 12 percent would bring forward launching dates, and 8 percent would begin a new job. Let us hope this time next year, they have the luxury of at least a little more time to attain those aims.