1.2 Audience and scope 1.3 Navigating the book Chapter 2, “Agile integration” on page 5 through Chapter 4, “Cloud-native concepts and  technology” on page 85 cover relatively deep architectural territory. But we aim to define all  terms and technologies that are mentioned so that it is suitable for any reader. Our  expectation is that many readers are a familiar with integration as a topic and have  experience with one or more integration technologies. We move relatively quickly over topics  that we expect that the reader knows.  Then, we focus on technology that empowers a modern integration journey. Chapter 5, “IBM  Cloud Pak for Integration” on page 143 introduces the core  integration capabilities. Chapter 6,  “Practical agile integration” on page 169 is written such that the scenarios should be readable  even where they involve capabilities in which you might not be a specialist. Chapter 7, “Field  notes on modernization for application integration” on page 433 through Chapter 9, “Field  notes on modernization for messaging ” on page 569 are written for specialists, and they  describe some of the common issues with typical modernization programs.  A single book cannot document integration modernization in its entirety, especially in a space  that is under such rapid evolution. For more information about this topic, see the following  resources: Chapter 2, “Agile integration” on page 5 explores the effect that digital transformation has on  both the application and integration landscape, and the limitations of previous techniques. We  describe what led us to this point, the pros and cons of service-oriented architecture (SOA)  and the enterprise services bus (ESB) pattern, the influence of APIs, and the introduction of  the microservices architecture. We also describe the current state of agile integration.  The various capabilities that are associated with integration provide differing contributions to  digital transformation. Chapter 3, “Agile integration: Capa bility perspectives” on page 41  explores three core technological perspectives: application integration, API management, and  messaging and events. And it describes how their usage is changing in the context of agile  integration.  Chapter 4, “Cloud-native concepts and technology” on page 85 provides a detailed  description of what it means to build solutions by using cloud-native techniques. These  concepts are the same for any type of component, so they have the same concerns for an  application developer as they do for someone implementing integration.  Chapter 5, “IBM Cloud Pak for Integration” on page 143 provides an overview of IBM Cloud  Pak for Integration, and describes recent advances that enable integration modernization.  Chapter 1. Introduction  3 GLYPH<SM590000> Agile Integration GLYPH<SM590000> API Management  GLYPH<SM590000> Application Integration  GLYPH<SM590000> Messaging and Events 