DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Software Design and Architecture
  3. Microservices
  4. Microservices vs. ESBs

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?

Antonio Abad user avatar by
Antonio Abad
·
Dec. 14, 16 · Opinion
Like (6)
Save
Tweet
Share
20.16K Views

Join the DZone community and get the full member experience.

Join For Free

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!

microservice Enterprise service bus

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

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Implementing Adaptive Concurrency Limits
  • Kotlin Is More Fun Than Java And This Is a Big Deal
  • DevSecOps Benefits and Challenges
  • Hackerman [Comic]

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: