01 — Team Topologies
Purpose
[stub: team-topologies]
See Also
- Building a Platform Team —
observability/07-org-and-narrative/building-a-platform-team.md
Metadata
| Author | Amit Singh |
| Scope | patterns |
Local graph
Linked from 5 notes
Infrastructure Platform Engineering
A book-shaped table of contents for infrastructure platform engineering: from infrastructure operations to self-service platforms, IaC foundations, Terraform/OpenTofu, cloud platform design, networking, identity, compute, storage, golden images, automation, governance, observability, reliability, enterprise platforms, anti-patterns, and MAANG interview prep — cross-linking existing sre/networks/kubernetes/patterns/internal-developer-platforms notes instead of duplicating them.
4 — Ownership Models
Ownership models, team, domain, business-unit, and product-based, and the trade-offs each makes for accountability at scale.
Patterns
A book-shaped table of contents for reusable engineering patterns spanning object-oriented design, enterprise architecture, distributed systems, messaging, APIs, cloud infrastructure, observability, security, concurrency, AI/agentic systems, and organizational design — grounded in production experience at scale.
2 — Team Topologies
Introduces the four fundamental team types from Team Topologies — stream-aligned, platform, enabling, and complicated-subsystem — and their interaction modes.
Platform Engineering Fundamentals
A book-shaped table of contents for platform engineering fundamentals: evolution and organizational foundations, platform-as-a-product thinking, core principles (self-service, golden paths, automation, APIs), design principles, the platform lifecycle, DORA/SPACE metrics, anti-patterns, enterprise governance, and MAANG interview prep — cross-linking existing sre/patterns/observability/projects notes instead of duplicating them.
Related notes
02 — Conway's Law
Inverse Conway Maneuver, Team APIs, and Cognitive Load — why a system's architecture mirrors its org chart, and how to design the org chart on purpose instead of by accident.
03 — Engineering Leadership Patterns
RFC Process, ADRs, Design Reviews, Technical Governance, and Architecture Council — the decision-making scaffolding that lets an organization make architecture calls without every one becoming a meeting.
Patterns
A book-shaped table of contents for reusable engineering patterns spanning object-oriented design, enterprise architecture, distributed systems, messaging, APIs, cloud infrastructure, observability, security, concurrency, AI/agentic systems, and organizational design — grounded in production experience at scale.
02 — Pattern Selection & Trade-offs
How to choose between competing patterns under real forces: naming the context, weighing trade-offs and consequences, composing multiple patterns together, and recognizing when a pattern has outlived its fit.