WebSphere

Title:

Microservices Architecture: Where Do ESBs, Messaging and APIs Fit?

Stream:

Microservices/Docker (4)

Speakers:

Kim Clark

Abstract:

This session explores the myths and realities of microservices in relation to integration architecture. Microservices are as much a new approach to application architecture as they are a return to well-known good practices of isolation and decoupling. The complexities are all the more apparent when comparisons are drawn with evolved integration architecture concepts. The "ESB" concept is often derided in microservices architecture. Is the pattern completely invalid or does it still have its place? Messaging is the silent but essential partner that is key to decoupling among microservice components. But what type of messaging should you use where? Where do APIs fit into the picture? What different categories of API are present?

Download:

3298_-_Microservices_and_how_they_relate_to_ESB_API_and_messaging_-_InterConnect_2017.pdf

Bio:

Kim Clark:

Kim has spent the last couple of decades working in the field helping customers implement the integration aspects of solutions tackling concepts such as SOA, BPM and APIs and microservices. He has a broad and deep knowledge of the architecture and design issues involved and of the related IBM products. As a result, he writes and presents regularly on design and architecture best practices in this space. In his current role he works as a strategist on IBM's integration portfolio shaping the future direction of the products, but he still spends much of his time assisting customers maturing their integration architecture. Recent articles include "The evolving hybrid integration reference architecture" https://ibm.biz/HybridIntRefArch and "Microservices, SOA, and APIs: Friends or enemies?" https://ibm.biz/MicroservicesVsSoa.
LinkedIn: https://www.linkedin.com/in/kimjulianclark

[image not found]