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

Microservices vs. ESBs

DZone's Guide to

Microservices vs. ESBs

Microservices have called into question the future of ESB, but how does the new architecture trend really affect the Enterprise Service Bus?

· Integration Zone
Free Resource

Share, secure, distribute, control, and monetize your APIs with the platform built with performance, time-to-value, and growth in mind. Free 90-day trial of 3Scale by Red Hat

Let’s start with a simple definition of both concepts.

“An  ESB is basically the integration of the new and the old, providing a central place for the services, applications, and IT resources in general that you want to connect.”

Image title

“A microservice architecture (vs. the legacy monolithic architecture) is an approach to developing a software application as a series of small services, each running autonomously and communicating with one another, for example through HTTP requests to their APIs.”

Image title

Microservices have called into question the future of ESB, but how does the new architecture trend really affect the Enterprise Service Bus?

It seems that the microservices have arrived to stay. More and more CIOs want to install this type of architecture in their projects. Microservices are perceived as the future of doing business. Many believe that it is a generational change promoted by digital transformation and think that ESB is becoming obsolete.

Are they right? Are microservices the new era of SOA?

Definitely. You have to take them into account. However, as for ESBs, no; they are still alive. We must adapt our concept of this architecture and can no longer understand the Integration Bus as a centralized and inflexible concrete structure for the whole company. When we talk about them today, we should think of a flexible, scalable, and well-distributed infrastructure in which we can incorporate, implement, and monitor any type of service in an agile and efficient way.

The ESB must fulfill a function of integration, coordination, routing, and monitoring of the business activity. Understanding the ESB in this way, we can build applications through services or microservices to solve the requirements and needs of a company. The services must be treated in an individualized way with a standardized interface to a platform with automatically scalable execution time.

Thus, these services are decoupled and scaled in a linear fashion on non-specialized hardware. This is the best way to understand an Enterprise Service Bus today. Microservices do not mean the death of ESBs if the latter are used in a suitable way, focusing on an architecture where services are the protagonists and not in a centralized architecture towards the Integration Bus itself.

We must not forget to integrate a gateway of services for security and exposure of services as an API gateway to external consumers. The services gateway can direct the integration of integrated services into the Bus, external service applications, and cloud services. Finally, we have to think twice if we really need this type of architecture. An Entreprise Service Bus only makes sense if our goal is to coordinate the actions or events that are happening in our services from a set of heterogeneous systems that we must integrate and present to the upper layers.

In conclusion, we can definitely assert that microservices do not make ESB an obsolete technology. In fact, both are perfectly compatible and can function in a coordinated way. Of course, for them, we must ensure that we work with a correct and updated Business Services Bus concept. If so, microservices together with ESB are a winning combination. They have not come to deprecate them; at most, they have come to be their accomplices to get a critical support architecture to the business!

Explore the core elements of owning an API strategy and best practices for effective API programs. Download the API Owner's Manual, brought to you by 3Scale by Red Hat

Topics:
microservices ,esb ,integration

Published at DZone with permission of Antonio Abad. See the original article here.

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}