Book description
The organization pursuing digital transformation must embrace new ways to use and deploy integration technologies, so they can move quickly in a manner appropriate to the goals of multicloud, decentralization, and microservices. The integration layer must transform to allow organizations to move boldly in building new customer experiences, rather than forcing models for architecture and development that pull away from maximizing the organization's productivity.
Many organizations have started embracing agile application techniques, such as microservice architecture, and are now seeing the benefits of that shift. This approach complements and accelerates an enterprise's API strategy. Businesses should also seek to use this approach to modernize their existing integration and messaging infrastructure to achieve more effective ways to manage and operate their integration services in their private or public cloud.
This IBM® Redbooks® publication explores the merits of what we refer to as agile integration; a container-based, decentralized, and microservice-aligned approach for integration solutions that meets the demands of agility, scalability, and resilience required by digital transformation. It also discusses how the IBM Cloud Pak for Integration marks a significant leap forward in integration technology by embracing both a cloud-native approach and container technology to achieve the goals of agile integration.
The target audiences for this book are cloud integration architects, IT specialists, and application developers.
Table of contents
- Front cover
- Notices
- Preface
- Chapter 1. Introduction
-
Chapter 2. Agile integration
- 2.1 Agile integration: A brief introduction
- 2.2 The journey so far: SOA, ESBs, and APIs
- 2.3 Microservices
- 2.4 The three aspects of agile integration
-
2.5 People: Decentralized integration ownership
- 2.5.1 Moving to a decentralized and business-focused team structure
- 2.5.2 Big bangs generally lead to big disasters
- 2.5.3 Decentralized integration ownership and decentralized infrastructures
- 2.5.4 Prioritizing project delivery first
- 2.5.5 Evolving the role of the architect
- 2.5.6 Automation: The key to consistency in decentralization
- 2.5.7 Producing multi-skilled developers
- 2.5.8 Conclusions on decentralized integration ownership
- 2.6 Architecture: Delivery-focused architecture
- 2.7 Technology: Cloud-native infrastructure
-
Chapter 3. Agile integration: Capability perspectives
- 3.1 Capability perspective: API management
-
3.2 Capability perspective: Application integration
- 3.2.1 Moving to a cloud-native approach
- 3.2.2 Fine-grained deployment: Breaking up the ESB
- 3.2.3 Grouping integrations
- 3.2.4 Stateless components
- 3.2.5 Image-based deployment
- 3.2.6 Elastic, agnostic infrastructure and container orchestration platforms
- 3.2.7 Lightweight run times: How the modern integration run time has changed
- 3.2.8 Log-based monitoring
- 3.2.9 API intra-application communication
- 3.2.10 Event-driven architecture
- 3.2.11 Agile methods
- 3.2.12 Continuous Integration and Continuous Delivery and Deployment
- 3.2.13 DevOps
- 3.2.14 Creating integrations is becoming easier
- 3.2.15 Decentralizing integration ownership
- 3.2.16 Using integration run times in a microservices application
- 3.3 Capability perspective: Messaging and event streams
- 3.4 Capability perspective: Files and Business-to-Business
- 3.5 Hybrid and multicloud considerations
- 3.6 Use cases driving hybrid and multicloud adoption
- 3.7 References
-
Chapter 4. Cloud-native concepts and technology
- 4.1 Defining cloud-native
-
4.2 Key elements of cloud-native applications
- 4.2.1 Modular components
- 4.2.2 Preferring stateless
- 4.2.3 Immutable deployment
- 4.2.4 Elastic, agnostic infrastructure and container orchestration platforms
- 4.2.5 Lightweight run times
- 4.2.6 Log-based monitoring
- 4.2.7 API-led intra-application communication
- 4.2.8 The reprise of event-driven architecture
- 4.2.9 Agile methods
- 4.2.10 Continuous Integration and Continuous Delivery and Deployment
- 4.2.11 Continuous Adoption
- 4.2.12 DevOps
- 4.3 Twelve-factor apps
- 4.4 Container technology: the current state of the art
- 4.5 Cloud-native is not for everyone, nor for everything
- 4.6 Realizing the true benefits of containerization
- 4.7 Application boundaries in a container-based world
- 4.8 Service mesh
- 4.9 Cloud-native security – an application-centric perspective
- 4.10 The future of cloud-native
-
Chapter 5. IBM Cloud Pak for Integration
- 5.1 IBM Cloud Pak for Integration
- 5.2 Red Hat OpenShift Container Platform
- 5.3 API Lifecycle: IBM API Connect
- 5.4 Integration security: IBM DataPower Gateway
-
5.5 Application integration: IBM App Connect
- 5.5.1 User-aligned integration tooling
- 5.5.2 No-code RESTful integration services
- 5.5.3 Flexible integration patterns
- 5.5.4 Broad deployment options
- 5.5.5 Extended connectivity
- 5.5.6 Situational awareness with insightful and actionable notifications
- 5.5.7 Quick utilization of artificial intelligence (AI) services
- 5.5.8 Rapid visual orchestration of data and systems for API-driven architectures
- 5.5.9 Lightweight integration runtime for cloud native deployment
- 5.5.10 Grown from a trusted market leading product
- 5.5.11 IBM App Connect on deployment options
- 5.6 Enterprise Messaging: IBM MQ
- 5.7 Event Streaming: IBM Event Streams
- 5.8 High-Speed File Transfer: IBM Aspera
- 5.9 Service Mesh: Istio
-
Chapter 6. Practical agile integration
- 6.1 Introduction
- 6.2 Application Integration to front a data store with a basic API
- 6.3 Expose an API using API Management
-
6.4 Messaging for reliable asynchronous data update commands
- 6.4.1 Enable create, update, delete via commands
- 6.4.2 Deploy and configure Queue Manager
- 6.4.3 Queue manager configuration
- 6.4.4 DB commands implementation
- 6.4.5 Graphical data maps implementation
- 6.4.6 Policy definitions
- 6.4.7 BAR file creation
- 6.4.8 Override policies for environment specific values
- 6.4.9 Global transaction coordination considerations
- 6.4.10 Conclusion
- 6.5 Consolidate the new IBM MQ based command pattern into the API
- 6.6 Advanced API security
- 6.7 Create event stream from messaging
- 6.8 Perform event-driven SaaS integration
-
6.9 Implementing a simple hybrid API
- 6.9.1 Business scenario
- 6.9.2 Invoking existing APIs from IBM App Connect Designer
- 6.9.3 Solution overview
- 6.9.4 Preparing the external SaaS applications
- 6.9.5 Create simulated on-premises API flow
- 6.9.6 Create Hybrid API
- 6.9.7 Test the flows
- 6.9.8 First, test the simulated on-premises API
- 6.9.9 Final Hybrid API integrated testing
- 6.9.10 Conclusion
-
6.10 Implement event sourced APIs
- 6.10.1 Implementing the query side of the CQRS pattern
- 6.10.2 Event sourced programming - a practical example
- 6.10.3 How to do it?
- 6.10.4 Creating the flow in IBM App Connect
- 6.10.5 Mapping the received events to the output required
- 6.10.6 Sending the new payload to the database
- 6.10.7 Client applications
- 6.11 REST and GraphQL based APIs
- 6.12 API testing
- 6.13 Large file movement using the claim check pattern
-
Chapter 7. Field notes on modernization for application integration
- 7.1 IBM App Connect adoption paths
-
7.2 Splitting up the ESB: Grouping integrations in a containerized environment
- 7.2.1 What grouping do you have today?
- 7.2.2 Splitting by business domain
- 7.2.3 What about integrations that span business domains?
- 7.2.4 Grouping within a domain
- 7.2.5 Stable requirements and performance
- 7.2.6 Synchronous versus asynchronous patterns
- 7.2.7 Shared lifecycle
- 7.2.8 A worked example
- 7.2.9 Conclusion
-
7.3 When does IBM App Connect need a local MQ server?
- 7.3.1 Benefits of being dependency-free in container-based environments
- 7.3.2 When can we manage without a local MQ server?
- 7.3.3 Can I talk to multiple queues in the same transaction without a local MQ server?
- 7.3.4 Coordinating a two-phase commit requires a local MQ server
- 7.3.5 When else do I need a local MQ server?
- 7.3.6 Why do we have so many integrations that use server connections?
- 7.3.7 Conclusion
- 7.4 Mapping images to helm charts
- 7.5 Continuous Integration and Continuous Delivery Pipeline using IBM App Connect V11 architecture
- 7.6 Continuous Adoption for IBM App Connect
- 7.7 High Availability and Scaling considerations for IBM App Connect in containers
-
7.8 Migrating centralized ESB to IBM App Connect on containers
- 7.8.1 Overview
- 7.8.2 Considerations for IBM MQ based integrations in containers
- 7.8.3 Considerations for Http/WebServices based integration flows in containers
- 7.8.4 Considerations for integrations that interact with databases
- 7.8.5 Considerations for in containers
- 7.8.6 Considerations for TCP/IP based integrations in containers
- 7.8.7 Considerations for file-based integration in containers
- 7.8.8 Considerations for integrating IBM App Connect with IBM Event Streams
- 7.9 Splitting an integration across on-premises and cloud
-
Chapter 8. Field notes on modernization for API lifecycle
- 8.1 Move from DataPower only to API Connect
- 8.2 Enterprise APIs across a hybrid or multicloud boundary
- 8.3 How many API Connect Clouds and Gateways
- 8.4 Organization, Catalog and Space responsibilities for APIs
- 8.5 Automated provisioning of a new API provider team
- 8.6 High availability and scaling on containers for API Management
- 8.7 IBM API Connect API Test Pyramid
- Chapter 9. Field notes on modernization for messaging
- Appendix A. Additional material
- Related publications
- Back cover
Product information
- Title: Accelerating Modernization with Agile Integration
- Author(s):
- Release date: July 2020
- Publisher(s): IBM Redbooks
- ISBN: 9780738458366
You might also like
video
An emerging architecture pattern for Agile integration: Cell-based architecture (sponsored by WSO2)
The number of microservices running in enterprises increases daily. As a result, service composition, governance, security, …
book
Event Processing: Designing IT Systems for Agile Companies
How to implement effective event-processing solutions Business people and IT professionals understand well the benefits of …
book
Agile Transformation: Using the Integral Agile Transformation Framework to Think and Lead Differently
Lead Agile Transformations that Scale and Succeed across the Entire Organization Most organizational leaders know agility …
article
Communicate with Stakeholders More Effectively
This selection of shortcuts will enable you to improve your communication, critical thinking, documentation, and networking …