Home Java The state of Java software development in 2021

The state of Java software development in 2021

10 min read

Perforce, supplier of Java instruments JRebel and XRebel, just lately introduced the outcomes of its ninth annual international Java developer productiveness report, based mostly on a survey of over 850 Java builders. Matters coated embody the character of Java groups, challenges they expertise, most well-liked instruments, and success of stated instruments and applied sciences. The important thing discovering reveals that regardless of growing use of microservices, builders are nonetheless dealing with lengthy redeploy instances and interservice performance points.

SEE ALSO: Java is immortal and feels good: 2020 outcomes and 2021 traits

Concerning the Respondents

The survey discovered 49% of respondents have been Java builders, with the remainder cut up throughout crew lead, architects, and consultants. 6% have been director, vice-president or C-Stage. It was good to listen to that everybody who responded is in work, with simply over a 3rd (36%) in an enterprise (bigger) organisation, 42% in small or medium-sized corporations, and 15% in start-ups. The bulk work in small groups, which is indicative of each a rising want for extra agile improvement and adoption of microservices, the place builders work with smaller segments of code. 40% of groups are between 3-9 individuals, 24% 10-20, and 17% 20-50 individuals.

Java and microservices traits

As anticipated, 69% of respondents are nonetheless utilizing Java 8, adopted by JavaScript at 40%, and Java 11 at 36% (observe that they have been allowed to pick out multiple programming language of selection). Solely 16% say they’re utilizing Java 12 or newer, and 15% are at present sticking with Java 7 or older.

Adoption of microservices stays regular, with 66% of respondents both actively transitioning to or at present utilizing microservices. Solely 13% of respondents should not planning to transition in any respect. Builders have been additionally requested what number of microservices that they had of their main purposes, on a scale of 1 to twenty. The solutions have been 36% utilizing 5-10 and 34% utilizing 1-5, adopted by 16% with 20 or extra and 14% with 10-20. After all, organisations can have multiple software structure, as an example: monolith remains to be utilized by 42%, SOA by 29%, cellular by 23%, and desktop by 18%.

Most Standard Instruments

The report surveyed respondents on their most used applied sciences and instruments in every class:

  • Utility servers – Tomcat nonetheless dominates at 66%. Then there’s a comparatively even unfold between JBoss/WildFly (19%), WebLogic (18%), Jetty (15%) and WebSphere (14%).
  • Utility framework – Spring Boot takes the highest slot at 62%, a lower from final 12 months’s 83%. Customers of DropWizard sit at 8% (a rise from 2020’s 1%); likewise Quarkus adoption grew from 1% to six%.
  • Framework configuration – Annotations is the outright chief at 75%, whereas 22% configure with code added to strategies that run throughout initialisation.
  • IDEs – IntelliJ IDEA is available in at primary with 65%, adopted by Eclipse (48%), VSCode (27%), and NetBeans (13%).
  • JRE/JDK distribution – Use of Oracle JDK went up — 59% in comparison with 50% final 12 months — regardless of experiences of individuals shifting away from it as a result of licensing prices. This may very well be attributable to the quantity of bigger enterprises who responded to the survey, as they typically discover transition tougher than smaller organisations. In second place is AdoptOpenJDK at 22% and an extra 10% report utilizing Amazon Corretto.
  • Databases – Probably the most favoured is MySQL at 43%, then Oracle DB and PostreSQL sharing second place at 36% every. Subsequent up was MongoDB, with 29% of respondents.
  • Construct instruments – Maven is the highest instrument of selection at 67%, whereas final 12 months, Maven and Gradle have been just about neck-and-neck.
  • Virtualisation instruments – 88% say they use these instruments, with far and away the commonest one being Docker at 57%, down from 74% final 12 months. Kubernetes is the runner-up at 42%, a step up from 35% 12 months in the past. VMWare sneaks in at third place with 27% (once more, a rise in comparison with 2020).
  • CI/CD – Jenkins stood out with 61% of respondents utilizing it, with others (Bamboo, TravisCI, TeamCity and others) at 12% or much less.
  • PaaS – Most respondents at the moment are utilizing a PaaS supplier, with solely 24% saying that they don’t. For many who use a PaaS supplier, AWS was the best choice at 39%. Microsoft Azure follows with 24% and Google Cloud with 18%.

SEE ALSO: What’s Rubbish assortment log, Thread dump, Heap dump?

Developer Ache Factors and Challenges

The largest software efficiency challenge cited was lengthy software response instances at 54% (which is on a par with final 12 months’s 55%). This persevering with development aligns with rising microservices adoption. The following highest efficiency points reported have been excessive CPU utilization (39%), and reminiscence leaks (35%), with extreme open connections and IO queries coming in at 26% and 19%, respectively.

Deployment instances are a standard space of grievance. 59% of builders expertise redeploy instances over 4 minutes, and 20% expertise redeploy instances longer than 10 minutes. There are two potential causes behind this. One is that when microservices develop in dimension, it takes longer to develop and create purposes. The second purpose is because of microservices working on distant virtualization machines.

Particular to microservices, troubleshooting inter-service performance was the most important reported problem at 30%, adopted by issues with establishing the event surroundings regionally (24%). This may be attributed to the difficulties of making a posh microservice software. In joint third place at 14% every are the challenges of troubleshooting inter-service efficiency points and scaling and monitoring in manufacturing.

Lastly, builders have been requested how they’d spend further time in the course of the workday ought to their challenges be mitigated. 1 / 4 of respondents stated they’d deal with bettering check protection, adopted by bettering software efficiency (21%). 19% say they’d add new options and 15% would spend these further minutes bettering the event course of. 12% would velocity up their launch cadence, 12% would convey ahead launch dates, and eight% would begin a brand new mission. Let’s hope that by this time subsequent 12 months, they’ve the luxurious of a minimum of a bit extra time to realize these objectives.

Leave a Reply

Your email address will not be published. Required fields are marked *

Check Also

Washoe County Community Development Public Workshop (via Zoom) on March 10, 2021 from 5:30 to 7:00 pm

Washoe County Neighborhood Growth Public Workshop (by way of Zoom) on March 10, 2021…