Chapter 37 Further Reading: The Hybrid Architecture

Tier 1: Verified IBM Documentation

These are primary sources available directly from IBM's documentation library.

Hybrid Architecture and Modernization

IBM z/OS Connect Documentation The current documentation for z/OS Connect, covering REST API creation, JSON/COBOL data transformation, CICS and IMS connectivity, and OpenAPI specification generation. The sections on interceptors and custom transformations are particularly relevant for building production ACLs that go beyond default data type mapping. Available at: IBM Documentation — z/OS Connect library (https://www.ibm.com/docs/en/zos-connect)

IBM Redbook: Accelerating Modernization with Agile Integration IBM Redbook SG24-8452. Covers integration patterns for hybrid mainframe-cloud architectures, including API management, event-driven architecture, and data integration. Chapters on z/OS Connect and MQ-based integration are directly relevant to Sections 37.2 and 37.3 of this chapter. Available at: IBM Redbooks (https://www.redbooks.ibm.com/)

IBM Redbook: z/OS Connect — A Practical Guide IBM Redbook SG24-8430. Step-by-step implementation guidance for z/OS Connect, including CICS service provider configuration, JSON schema customization, and performance tuning. Essential reading for anyone implementing the ACL pattern described in Section 37.2. Available at: IBM Redbooks

IBM Mainframe Modernization Documentation IBM's hub for mainframe modernization resources, covering IBM Wazi, z/OS Connect, IBM Cloud Pak for Integration on z/OS, and the broader modernization methodology. Includes reference architectures that align with the patterns discussed in this chapter. Available at: IBM Documentation (https://www.ibm.com/cloud/mainframe-modernization)

Data Integration and CDC

IBM InfoSphere Data Replication Documentation The primary reference for CDC from DB2 on z/OS. Covers log-based change capture, transformation rules, target database configuration, and monitoring. The sections on latency management and performance tuning are directly relevant to Section 37.3's discussion of CDC lag management. Available at: IBM Documentation — InfoSphere Data Replication library

IBM Redbook: Implementing IBM InfoSphere DataStage and QualityStage on z/OS IBM Redbook SG24-7830. While focused on DataStage, the early chapters on z/OS data integration patterns and CDC architecture provide useful context for the shared-nothing data architecture pattern. Available at: IBM Redbooks

Messaging and Event Architecture

IBM MQ Documentation: Connecting IBM MQ to Apache Kafka IBM's official documentation for the IBM MQ Kafka connector (source and sink). Covers configuration, message transformation, error handling, and exactly-once delivery semantics. Essential for implementing the event mesh pattern from Section 37.2. Available at: IBM Documentation — IBM MQ library (https://www.ibm.com/docs/en/ibm-mq)

IBM Redbook: IBM MQ as a Service on Cloud IBM Redbook SG24-8468. Covers IBM MQ on cloud platforms (AWS, Azure, IBM Cloud) and hybrid MQ topologies where queue managers on z/OS communicate with cloud-hosted queue managers. Directly relevant to the MQ-to-cloud messaging patterns discussed in this chapter. Available at: IBM Redbooks

Security

IBM z/OS Security Server RACF Documentation IBM Publication SA23-2289 (various volumes). The authoritative reference for RACF configuration. The sections on PassTickets, identity mapping, and surrogate user IDs are directly relevant to the identity federation patterns in Section 37.5. Available at: IBM Documentation — z/OS library

IBM Redbook: Security on z/OS IBM Redbook SG24-7210. Comprehensive coverage of z/OS security architecture, including AT-TLS configuration, ICSF cryptographic services, and integration with external identity providers. The chapters on network security and cryptographic key management are essential reading for the zero-trust model described in Section 37.5. Available at: IBM Redbooks

Tier 2: Attributed Community and Industry Sources

Architecture Patterns

"Domain-Driven Design" by Eric Evans Addison-Wesley, 2003. The original source for the anti-corruption layer pattern. Chapter 14 ("Maintaining Model Integrity") introduces the ACL as a pattern for protecting a domain model from corruption by external systems. While the book focuses on object-oriented design, the ACL concept translates directly to hybrid mainframe-cloud integration.

"Building Microservices" by Sam Newman (2nd Edition) O'Reilly, 2021. Chapters on integration patterns, data consistency (sagas, eventual consistency), and organizational design provide the distributed systems foundation for hybrid architecture. The chapter on the strangler fig pattern (also covered in our Chapter 33) shows how the pattern works with API gateways.

"Designing Data-Intensive Applications" by Martin Kleppmann O'Reilly, 2017. The definitive reference for data consistency patterns in distributed systems. Chapters 7 (Transactions), 9 (Consistency and Consensus), and 11 (Stream Processing) provide the theoretical foundation for the data consistency patterns in Section 37.3. The discussion of CDC and event sourcing is particularly relevant.

"Enterprise Integration Patterns" by Gregor Hohpe and Bobby Woolf Addison-Wesley, 2003. The canonical reference for messaging-based integration patterns. While predating cloud-native architecture, the patterns (message channel, message translator, content-based router) are directly applicable to the event mesh and MQ-based integration discussed in this chapter.

Hybrid Architecture Case Studies and Industry Analysis

Gartner: "Modernization of Legacy Systems" (annual report series) Gartner's annual reports on mainframe modernization provide industry data on modernization project success rates, cost benchmarks, and strategy trends. The data on project failure rates cited in Chapter 32 draws from this body of work. Access requires Gartner subscription.

Forrester: "The State of Mainframe Modernization" Forrester's research on mainframe modernization strategies, including hybrid architecture adoption rates and vendor landscape analysis. Useful for benchmarking your organization's hybrid maturity against industry peers. Access requires Forrester subscription.

SHARE Conference Proceedings — https://www.share.org SHARE's semi-annual conferences include dedicated tracks on mainframe modernization and hybrid architecture. Presentations by IBM engineers and enterprise architects from organizations like banks, insurance companies, and government agencies provide real-world examples of the patterns discussed in this chapter. Search proceedings for "hybrid," "modernization," and "z/OS Connect."

Open Mainframe Project — https://www.openmainframeproject.org The Linux Foundation's Open Mainframe Project publishes open-source tools and best practices for mainframe modernization. The Zowe project (open-source z/OS interface framework) and COBOL Programming Course are relevant community resources.

Distributed Systems Theory

"The CAP Theorem" — Eric Brewer The original 2000 keynote and 2012 retrospective article ("CAP Twelve Years Later: How the 'Rules' Have Changed," IEEE Computer). Understanding CAP is essential for making informed data consistency decisions at the mainframe-cloud boundary. The key insight for hybrid architects: the mainframe side (DB2 with coupling facility) achieves CA (consistency + availability) within the Sysplex because the coupling facility provides a reliable shared state mechanism. Across the WAN to cloud, you're in AP territory (availability + partition tolerance), and must accept eventual consistency.

"Sagas" — Hector Garcia-Molina and Kenneth Salem The original 1987 paper from ACM SIGMOD that introduced the saga pattern for long-lived transactions. While written in the context of single-database systems, the compensation-based approach is the theoretical foundation for the cross-platform saga pattern described in Section 37.3.

Monitoring and Observability

"Site Reliability Engineering" by Google (Betsy Beyer et al.) O'Reilly, 2016. Chapter 6 ("Monitoring Distributed Systems") introduces the four golden signals (latency, traffic, errors, saturation) used in Section 37.4's unified monitoring model. The SRE principles of service-level objectives and error budgets are directly applicable to hybrid operational models.

"Distributed Systems Observability" by Cindy Sridharan O'Reilly, 2018. Covers observability principles (metrics, logs, traces) for distributed systems. The discussion of distributed tracing and correlation IDs provides context for the cross-platform tracing approach described in Section 37.4.

Tier 3: Vendor and Technology References

These references cover specific technologies used in the reference architecture. They are included for practical implementation guidance but should be evaluated for vendor bias.

Apache Kafka Documentation — https://kafka.apache.org/documentation Comprehensive documentation for Kafka configuration, topic management, consumer groups, and exactly-once semantics. Relevant for the cloud side of the event mesh pattern.

Kong Gateway Documentation — https://docs.konghq.com Documentation for the Kong API gateway used in CNB's reference architecture. Covers routing, authentication plugins, rate limiting, and analytics.

AWS API Gateway Documentation — https://docs.aws.amazon.com/apigateway Documentation for the managed API gateway used in SecureFirst's architecture. Covers REST API creation, Lambda integration, usage plans, and CloudWatch integration.

Grafana Documentation — https://grafana.com/docs Documentation for the unified monitoring dashboard platform. Covers Prometheus integration, custom data sources, dashboard design, and alerting rules.

HashiCorp Vault Documentation — https://developer.hashicorp.com/vault Documentation for secrets management that some hybrid architectures use for managing credentials that span platforms. Relevant to the identity and security patterns in Section 37.5.

Suggested Reading Order

For readers implementing a hybrid architecture for the first time:

  1. "Designing Data-Intensive Applications" (Kleppmann) — Chapters 7, 9, 11 (distributed data theory)
  2. IBM z/OS Connect Documentation — Getting Started guide (ACL implementation)
  3. IBM MQ Kafka Connector Documentation (event mesh implementation)
  4. IBM InfoSphere Data Replication Documentation (CDC implementation)
  5. "Site Reliability Engineering" (Google) — Chapter 6 (monitoring golden signals)
  6. IBM Redbook: Accelerating Modernization with Agile Integration (reference architectures)
  7. "Building Microservices" (Newman) — Chapters on integration and organizational design
  8. "Domain-Driven Design" (Evans) — Chapter 14 (anti-corruption layer theory)

This sequence should take approximately 40-60 hours of focused reading and provides both the theoretical foundation and the practical implementation guidance for hybrid architecture design.