Chapter 26 — Architectural Intersections

Core ideas

• Architecture doesn’t exist in isolation — it intersects with adjacent disciplines the modern architect must engage: data/data architecture (operational vs. analytical data, the data mesh idea), security, user experience, DevOps/platform engineering, and enterprise architecture.
• The chapter’s thrust: the boundaries of the architect role are widening; effective architects build bridges to these adjacent roles rather than treating them as someone else’s problem.

Trade-offs to argue

Depth in your own domain vs. sufficient literacy in each adjacent one. You can’t be an expert in all; you must be conversant enough to collaborate and make trade-offs across the seams.

Note: The exact set of intersections may differ slightly in your copy — list the ones your edition names and jot one architectural implication for each.