From the Enterprise Service Bus to Microservices

17

Dealing with legacy is one of the most common areas of conversation we have around “cloud native” and Pivotal Cloud Foundry. I wrote up a basic framing for how to think of legacy applications last year as part of my cloud-native journey series, and in reviewing talks for the upcoming SpringOne Platform conference I’ve noticed that it’ll be one of the topics at that event this August.

Pivotal architect Rohit Kelapure has been working on this topic a lot and has written a white paper on migrating from Enterprise Service Bus (ESB)-based legacy architectures. After working with him on the paper a tad, I had a few questions whose answers I thought would be helpful to share for all those folks who ask about this topic.

Coté: Technology choices often start with the best of intentions. Few people want to make a bad system. Whats driven so many organizations to choose ESBs?

Rohit: ESBs are a response to enterprise needs around service integration, audit, transformation, business impact traceability, composability, data transformation and a central point for governance….

Read more at The New Stack