Team Topology Example
This example demonstrates using team topology patterns with services, layers, and cross-domain metrics.
Document Overview
The example includes:
- Teams of different types (stream-aligned, platform, overlay)
- Services owned by teams
- Metrics across operations, security, and quality domains
- Layer accountability assignments
Key Concepts
Team Types
The example includes all four team topology types:
| Type | Example Team | Purpose |
|---|---|---|
| Overlay | Security Team, QE Team | Define domain standards |
| Platform | Platform Engineering | Provide infrastructure |
| Stream-Aligned | Payments Team, Users Team | Build and run services |
Service Ownership
Stream-aligned teams own services:
{
"id": "payments-team",
"name": "Payments Team",
"type": "stream_aligned",
"serviceIds": ["payments-api", "payments-worker"]
}
Layer Accountability
Teams declare which layers they're accountable for:
Services
| Service | Owner | Layer | Tier |
|---|---|---|---|
| kubernetes-platform | Platform Engineering | infra | tier1 |
| observability-stack | Platform Engineering | infra | tier1 |
| payments-api | Payments Team | runtime | tier1 |
| payments-worker | Payments Team | runtime | tier2 |
| users-api | User Management Team | runtime | tier1 |
Download
See Also
- Teams Concept - Understanding team topology
- Services Concept - Understanding the service model
- prism team - CLI commands for teams
- prism service - CLI commands for services