×

Get the Paper

First Name
Last Name
Company
Country
State- optional
Job Title / Role
Thank you!
Error - something went wrong!
   

Migrating an ESB to a Cloud-Native Platform

December 2, 2016

Overview

The rising popularity of microservices has led to several questions around the role of ESBs. Traditionally the role of the ESB was to fulfill the promise of SOA by providing invocation, routing, mediation, messaging, process choreography, service orchestration, and the other services needed for large, enterprise architectures.

Many organizations have fully developed and very mature ESBs in place to handle the services needed for their applications. As these organizations are looking at the microservices approach, they're finding conflicts between the two approaches. For example, microservices favor dumb pipes and smart endpoints, whereas an ESB often works on an canonical data representation leading to dumb endpoints and smart pipes.

For organizations looking resolve these conflicts, this whitepaper follows a 5 step process that can be put in place to evolve your ESB infrastructure to a next generation microservices based one. Each of the five steps (coexist, lift & shift, refactor, replace, and transform) are covered in detail, as well as motivations for going through this architectural evolution.

Previous
EMC Solution For Agile And Robust Analytics On Hadoop – Data Lake With Pivotal HBD
EMC Solution For Agile And Robust Analytics On Hadoop – Data Lake With Pivotal HBD

Next
Introducing The Newly Redesigned Apache HAWQ (incubating)
Introducing The Newly Redesigned Apache HAWQ (incubating)