A comparison of key integration and application architecture concepts for an evolving enterprise. Do microservices force us to look differently at the way we lay down and evolve our integration architecture, or are they purely about how we build applications? Are microservices a new concept, or an evolution of the many ideas that came before them? What is the relationship between microservices and other key initiatives such as APIs, SOA, and Agile. In this session, we will unpack what microservices really are, and indeed what they are not. We will consider whether there is something unique about this particular point in time technologically that has enabled microservice concepts to take hold. Finally, we will look at if, when, where and how an enterprise can leverage the benefits of microservices principles. Speakers: Kim Clark 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