Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

DZone Research: Additional Considerations for Java

DZone's Guide to

DZone Research: Additional Considerations for Java

When it comes to the Java ecosystem, it's important to keep in mind its inherent strengths, the flexibility of the JVM, and public participation.

· Java Zone ·
Free Resource

How do you break a Monolith into Microservices at Scale? This ebook shows strategies and techniques for building scalable and resilient microservices.

To gather insights on the current and future state of the Java ecosystem, we talked to executives from 14 companies. We began by asking, "What have I failed to ask you that you think we need to consider about the Java ecosystem?" Here's what the respondents told us:

  • One of the strengths of Java that I think is very undervalued is that it is a very small language that doesn’t offer a huge range of options for how to do things. As a result, if two engineers write the same solution for the same problem with Java, they tend to end up with the same piece of code. That’s a really strong advantage that Java has that is not true in many other competing languages, and it’s one of the great strengths that I’m not sure people continue to recognize. A lot of newer languages are falling into the trap that you can write the same piece of code eight different ways and it will do the same thing, but because they are coded completely differently it makes it much harder for a human to understand. 
  • Your participation matters in the continued consistency, stability, and security of the Java ecosystem.
  • We need to recognize the importance of open source – embrace it and contribute to it where we can. Java and open source both have a bright future. If you find problems, work on fixing them. It’s a great community and it’s made better when everyone is involved and contributing.
  • Containers are changing how developers deploy applications and that affects Java applications.
  • Pay attention to Kotlin which runs on the JVM. Adopt new languages to help create new applications. There’s a lot of really smart people in the ecosystem, pay attention to what they have to say. There’s a lot to continue learning as things will always change.
  • Struggles managing dependencies. Node came along and it’s still a mess. What is the future of dependencies and dependency management?
  • Enterprise Java’s future has been handed off to Eclipse. This is a good thing for innovation and integration.

Here’s who we spoke to:

  • Gil Tayar, Senior Architect and Evangelist, Applitools
  • Frans van Buul, Commercial Developer, Evangelist, AxonIQ
  • Carlos Sanches, Software Engineer, CloudBees
  • Jeff Williams, Co-founder and CTO, Contrast Security
  • Doug Pearson, CTO, FlowPlay
  • John Duimovich, Distinguished Engineer and Java CTO, IBM
  • Brian Pontarelli, CEO, Inversoft
  • Wayne Citrin, CTO, JNBridge
  • Ray Augé, Sr. Software Architect, Liferay
  • Matt Raible, Java Champion and Developer Advocate, Okta
  • Heather VanCura, Chair of the Java Community Process Program, Oracle
  • Burr Sutter, Director Developer Experience, Red Hat
  • Ola Petersson, Software Consultant, Squeed
  • Roman Shoposhnik, Co-founder, V.P. Product and Strategy, Zededa
  • How do you break a Monolith into Microservices at Scale? This ebook shows strategies and techniques for building scalable and resilient microservices.

    Topics:
    java ,kotlin ,java ecosystem ,eclipse ,containerization ,open source

    Opinions expressed by DZone contributors are their own.

    {{ parent.title || parent.header.title}}

    {{ parent.tldr }}

    {{ parent.urlSource.name }}