The State of Microservices Survey 2017 – Eight trends you need to know

During the fall of 2017, we conducted a microservices survey with our Red Hat Middleware and Red Hat OpenShift customers. Here are eight interesting trends discerned by the results:

1. Microservices are being used to re-architect existing applications as much as for brand new projects

There seems to be a strong emphasis in the market by technology vendors for positioning microservices as being only for new projects.  However, our survey reveals that organizations are also using microservices to re-architect existing and legacy applications.

Sixty-seven percent of Red Hat Middleware customers and 79 percent of Red Hat OpenShift customers indicated this. This data tells us that microservices offer value to users all along their IT transformation journey — whether they are just looking to update their current application portfolio or are gearing up new initiatives. So, if you are only focused on greenfield projects for microservices, it may be a good idea to also start evaluating your existing applications for a microservice re-architecture analysis. Microservices introduce a set of benefits that our customers have already started seeing, and they are applying these benefits not just to new projects but to existing ones as well.

Continue reading “The State of Microservices Survey 2017 – Eight trends you need to know”

Red Hat partners guide your journey to cloud-native development

The big question is always, “Do we car manufacturers learn to become tech companies more quickly than a tech company learns to be an automotive player?”

That is quite a statement. When a leading car manufacturer worries about being disrupted by a technology company, you know something big is going on. No wonder so many companies are talking about disruption these days.

There is a big transition taking place. And it is not just about competition. Or innovation. Or value migration. Or the creation of new markets. It is about the fact that every company is becoming a technology company, and only those that embrace this will survive, thrive, and shape our world. Software is at the core of this change, and increasingly it appears that the cloud is where much of this is going to take place.

Customers often come to us asking, “How can I be faster? How can I innovate and lead, instead of repeat and follow? How can I do that with enterprise-grade security, reliability and resiliency?”

A good part of the answer lies in using the cloud to power business models and help run, migrate, or scale existing applications, or develop new cloud-native ones. Red Hat has offered platforms to run customers’ applications and infrastructure in the cloud for a number of years. Today, we are taking another step forward by offering cloud-native application runtimes and frameworks, fully supported and enterprise grade.

Red Hat OpenShift Application Runtimes offers a curated selection of popular cloud-native application runtimes and frameworks that are well-suited for enabling cloud-native application development.

In the words of Joe Dickman, senior vice president of Vizuri, “Red Hat OpenShift Application Runtimes establishes a foundation for building services for hybrid and multi-cloud application and systems […] in a myriad of environments using their preferred tools.”

With Red Hat OpenShift Application Runtimes, organizations can innovate directly in the cloud, from inception to production; running in the industry’s most comprehensive Kubernetes platform, Red Hat OpenShift Container Platform, and in a cloud provider of choice.

James Chinn, CEO at Shadow-Soft, adds: “With Red Hat’s latest support of Wildfly Swarm, Spring Boot, and NodeJS, our customers can feel confident building and scaling containerized workloads on OpenShift. Openshift deployed in a public cloud gives our customers the flexibility and agility to deploy an enterprise and container framework quickly and easily.”

When customers develop an application strategy for moving to the cloud, they have to choose the right runtimes, based on factors such as existing skills or the right framework for the application they need to create.

“Historically, one of the biggest challenges has been the roadmap necessary for change in legacy environments,” says Chris Hart, chief technology officer of Levvel. “OpenShift Application Runtimes helps simplify that transformation and lowers the effort and risks to getting started with cloud-native development.”

They need to decide which applications to move to the cloud and how to keep evolving and innovating. What applications get a lift-and-shift (rehost) versus reshape or re-architect? Should they create “fast monoliths” or decompose them, totally, or partially, as microservices? If so, what is the right framework for the job?

Erik Melander, EVP of solutions at Kovarus, expands on this: “Red Hat OpenShift Application Runtimes […] reduces friction by packaging and supporting a curated set of open application runtimes and letting developers make the right choice for cloud-native development.”

It is also important for them to learn about containers and how to implement DevOps methodologies and culture. Development and operations teams may need to learn new skills and change the way they work.

We are happy to have a large network of partners around the world with the expertise to support our customers along the exciting path of going to the cloud. From the top level strategy and innovation consulting, down to the most detailed testing and infrastructure set up. From defining and helping implement an application modernization strategy, to helping implement and deploy a microservices architecture.

Red Hat solution systems integrators and solution providers can help select the right option based on the technical objectives, existing skills or strategy. They can also help customers prepare for the challenges of complex microservices architectures and equip an organization to adopt DevOps practices and culture.

Start your journey here!

Supporting quotes:

“For our customers that are developing applications to create and sustain competitive advantage, developer productivity is an ever-present challenge. We are excited to see Red Hat addressing this problem with the launch of Red Hat OpenShift Application Runtimes, which reduces friction by packaging and supporting a curated set of open application runtimes and letting developers make the right choice for cloud-native development.”
Erik Melander, EVP of Solutions at Kovarus

“We’re excited about Red Hat OpenShift Application Runtimes because it simplifies the adoption of beneficial technologies for our enterprise customers. Many companies know they need to achieve higher release velocity and improved reliability using approaches like microservices architecture and more modern development and operations tools. Historically, one of the biggest challenges has been the roadmap necessary for change in legacy environments. The OpenShift Application Runtimes help simplify that transformation and lowers the effort and risks to getting started with cloud-native development. We’re looking forward to seeing this accelerate our customers’ success.”
Chris Hart, Chief Technology Officer, Levvel

“We are excited about the announcement of Red Hat OpenShift Application Runtimes as it signals Red Hat’s continual commitment to meeting our customers where they are today and positioning them for success in the future. With Red Hat’s latest support of Wildfly Swarm, Spring Boot and NodeJS, our customers can feel confident building and scaling containerized workloads on OpenShift. Openshift deployed in a public cloud gives our customers the flexibility and agility to deploy an enterprise and container framework quickly and easily. And like any public cloud deployment, you can start small and scale elastically as workloads demand.”
James Chinn, CEO, Shadow-Soft

“Organizations that are investing time and resources in cloud-native architectures must look at leveraging containerized workloads to provide a robust, flexible and reliable infrastructure that can respond quickly to changing customer needs. Red Hat OpenShift Application Runtimes establishes a foundation for building services for hybrid and multi-cloud application and systems in a programmable way that provision and decommission infrastructure and applications resources in a myriad of environments using their preferred tools.”
Joe Dickman, Senior Vice President, Vizuri

 

Eclipse MicroProfile 1.2 is Now Available

Eclipse MicroProfile, an open forum to collaborate on enterprise Java™ microservices, today announced the release of Eclipse MicroProfile 1.2.

Eclipse MicroProfile 1.2, which builds on the 1.1 version, updates the config API and adds the health check, fault tolerance, metrics, and JWT propagation APIs.

Continue reading “Eclipse MicroProfile 1.2 is Now Available”

Introducing OpenShift Application Runtimes Public Beta

Executive Summary

  • Red Hat OpenShift Application Runtimes is now in public beta, meaning you can try it!
  • Red Hat OpenShift Application Runtimes includes a collection of supported application runtimes.
  • Each runtime is designed to simplify cloud-native development by using Red Hat OpenShift capabilities in a manner natural to the language runtime.
  • Try it! Go to developers.redhat.com/rhoar. Choose an example and runtime, and watch it get forked to your github account and deployed to OpenShift. Feedback welcome on StackOverflow.

Continue reading “Introducing OpenShift Application Runtimes Public Beta”

The future of Java EE

At this stage the future of Java EE looks brighter than it has for quite a while as Oracle, working with Red Hat, IBM, other vendors and the wider community to move the specifications, TCKs and overall innovation to an open source foundation. I think in general most people in the Java community see this as positive but there are a few naysayers, even more of them in other non-JVM areas. The common thread throughout is along the lines of “who cares these days?” or “it’s far quicker and easier to accomplish the same things with framework X or language Y, anyway.” I’m not going to try to address all of the concerns which have been raised because many of the comments I’ve seen have clearly been subjective and bordering on click bait. However, I’m writing this piece to reiterate some things I’ve said over the years and which remain just as relevant today, in my opinion

I want to start though by saying that in all of this I am trying to remain objective. Of course in my current role I and Red Hat have a vested interest in Java EE but if you’ve known me long enough over the years you’ll know that I’m also a scientist and as such I base my opinions on observations and facts born out by those observations. If a fact or piece of data goes against a theory then I don’t ignore it, I review and likely update or replace the theory to match the facts. I’ve changed my opinion on many things throughout my career and I’m sure I will do so again.

OK so back to Java EE. Does this move to open source help the wider community? Is Java EE still relevant or has it had its day like so many technologies before it? I’m not going to link to other things I’ve written on Java EE and its future over the years as they’re easily searchable through your favourite engine. But in short, many people forget that Java EE represents an evolution of essential middleware capabilities which many mission critical applications require. It’s had a lot of bad press since its inception, some of it accurate and some of it less so. I think one of its big failings is that, like my favourite topic of transactions, it has been used and misused in environments where it wasn’t really appropriate. No stack or framework is going to be applicable to every problem space and of course developers are going to get frustrated if they try it and find it wanting and failing as a result.

Continue reading “The future of Java EE”

Eclipse MicroProfile continues its growth in the market

Organizations that have already embarked or are thinking about starting a digital transformation journey are assessing and looking for ways to leverage their Java EE expertise. IT development and operations have built Java expertise over years, and there is a challenge to balance their existing skill base with new digitally transformative technologies, such as microservices, APIs, container-based architectures, and reactive programming. Eclipse MicroProfile is an open source project and one of those digitally transformative technologies that enables and optimizes the development of microservices — using familiar Java EE technologies and APIs.

You can think of MicroProfile as minimal standard profile for Java microservices. As with Java EE, MicroProfile implementations across different vendors are fully interoperable.

MicroProfile is supported in WildFly Swarm on the recently announced Red Hat OpenShift Application Runtimes, our polyglot runtime platform powered by OpenShift, Kubernetes, and OpenStack. This delivers on the goal of simplifying the inherent complexity of developing cloud native applications.

There are a lot of reasons to begin adopting MicroProfile:

  • Open source, of course
  • Agility in developing microservices
  • Ability to leverage innovation
  • Architectural interoperability across different vendor offerings
  • No vendor lock-in
  • Fast learning curve for Java EE users (Java EE users can leverage their knowledge when using MicroProfile)
  • Ability to run on Red Hat OpenShift Application Runtimes 

Since MicroProfile was announced in June 2016, a lot has happened.  MicroProfile v 1.0 was released on September 19, 2016. Its implementation interoperability was demonstrated on November 2016 at Devoxx, where Red Hat, IBM, Tomitribe, and Payara demoed a unified web application with underlying microservices which had been developed separately by each vendor using MicroProfile. In addition, MicroProfile became part of the Eclipse Foundation as an incubation project back in December 14, 2016. New members have joined MicroProfile, such as SOUJava, Hazelcast, Fujitsu, Hammock, and kumuluzEE (the complete list of members can be found here).

Future releases of MicroProfile will build upon the existing foundation with organic growth by adding configuration, security, health check, and fault tolerance APIs, as well as adding support for later versions of CDI, JAX-RS, and JSON-P. The MicroProfile open source project plans to put out releases on an agile schedule and based on feedback from the open source community, which is accessible to everyone. Join the conversation and check out the MicroProfile site.

Announcing the Alpha release of Red Hat OpenShift Application Runtimes

Today Red Hat announced the alpha release of Red Hat OpenShift Application Runtimes (RHOAR). This is the first of many articles on the subject that will be published on the JBoss Middleware blog.

So what is RHOAR?

RHOAR provides application developers with a variety of application runtimes running on the OpenShift Container Platform. Specifically, the following application runtimes will be included in RHOAR:

  • Red Hat JBoss Enterprise Application Platform (EAP) – existing Java EE / Spring apps.
  • WildFly Swarm running MicroProfile – Java EE centric MSA
  • Spring Boot / Cloud – Spring centric MSA
  • Vert.x – greenfield reactive Java
  • Node.js – greenfield reactive JavaScript

Continue reading “Announcing the Alpha release of Red Hat OpenShift Application Runtimes”

It’s Official: MicroProfile Is Now Eclipse MicroProfile

MicroProfile is a community project with the mission of optimizing Enterprise Java for a microservices architecture.  In a short period of time, MicroProfile has reached three important milestones:

  1. June 27, 2016: Red Hat, IBM, Tomitribe, Payara and the London Java Community announced MicroProfile at DevNation.
  2. September 19, 2016: MicroProfile 1.0 was released at JavaOne 2016 with 5 implementations (and a 6th planned). The SouJava community joined to support the effort and Hammock was added as a implementation.
  3. December 14, 2016: The Eclipse Foundation Board approved the MicroProfile proposal, meaning that Eclipse MicroProfile is now an Eclipse incubator project. Mike Milinkovich, Eclipse Foundation Executive Director,  informed the community shortly after the vote.

The community is having active discussions on process (project evolution) and microservice APIs like application configuration, monitoring, health check, messaging, circuit breakers, and more.  Some discussions are even backed by real (proof of concept) code! The MicroProfile community is currently planning its next release. Feel free to join the discussion and help define the future of Enterprise Java microservices!