Tagged articles
team-topology
10 articles · Page 1 of 1
This article explains why effective service boundaries require aligning business rules, data ownership, change rhythms, and team responsibilities—not just drawing boxes around nouns—using a refund processing case study to compare modular monolith vs. microservice trade-offs and verify boundaries through concrete evidence.
Architecture DesignBounded ContextData Ownership
0 likes · 21 min read

This article dissects orchestration-driven SOA, a 1990s enterprise architecture pattern centered on a central ESB and strict service taxonomy, explaining its layered topology, how reuse led to tight coupling and bloated models, the difficulties of distributed transactions, and why its failures directly inspired modern microservices principles.
ESBSOAcoupling
0 likes · 18 min read

This article explores service-based architecture as a practical distributed architecture style that offers independent deployment benefits without the complexity of microservices, covering its topology, domain services, API gateway, data topology, risks, characteristic scores, suitable scenarios, and team topology alignment.
ACID transactionsdistributed architecturedomain-driven design
0 likes · 12 min read

This article explores microkernel architecture, detailing its core system and plug-in components, registry mechanisms, risk factors, characteristic scores, suitable and unsuitable scenarios, and team topology alignments for product-based and highly customizable business systems.
core systemmicrokernel architectureplug-in architecture
0 likes · 12 min read

This article explores modular monolith architecture, comparing monolithic vs modular structures, peer-to-peer vs mediator communication patterns, characteristic ratings (cost, simplicity, modularity, deployability, maintainability, elasticity, fault tolerance), suitable and unsuitable scenarios, and aligned team topologies based on Fundamentals of Software Architecture.
domain-driven designmediator patternmodular monolith
0 likes · 7 min read

This article explains the layered architecture style, its standard four-layer model, the trade-offs between closed and open layers including the architecture sinkhole anti-pattern, characteristic scoring for when to use or avoid it, and how it aligns with different team topologies.
Architecture Patternsarchitecture-sinkholefundamentals
0 likes · 6 min read


DevOpsJun 30, 2023 · R&D Management
This article explains how team topology and Conway's Law shape communication structures, describes the concepts of flow, enabler, and complicated‑subtle teams, and offers practical guidance on aligning team cognition, applying cognitive load theory, and building value‑stream teams to improve DevOps efficiency.
Conway's LawValue Streamcognitive load
0 likes · 24 min read


DevOpsJul 22, 2019 · Operations
This article explains the various DevOps team topologies—including anti‑patterns A‑G and nine positive types—detailing their characteristics, applicability, and potential effectiveness so organizations can select the most suitable structure for their value‑stream delivery goals.
Anti-PatternDevOpsOperations
0 likes · 14 min read

This article examines common DevOps team structures and anti‑patterns, explains how product portfolio, leadership, and organizational readiness influence the choice of topology, and presents nine practical models—from collaborative teams to SRE and container‑driven approaches—to help you select the most effective structure for your business.
CollaborationSREteam-topology
0 likes · 19 min read

This article examines how different DevOps team topologies and anti‑patterns affect value delivery, outlines key factors such as product portfolio and leadership, and evaluates nine concrete models—from collaborative development‑ops teams to container‑driven and SRE approaches—to help you choose the most effective structure for your organization.
DevOpsorganizational structuresoftware delivery
0 likes · 18 min read
