c4-level2-container
C4 Level 2: Container Diagram & Infrastructure Mapping
The Container diagram represents the high-level technical architecture (web apps, mobile apps, databases, background jobs).
🎯 Stakeholder Focus
- Architects: High-level tech decisions and API boundaries.
- Developers: High-level system structure and cross-app communication.
- Ops/DevOps: Deployment strategy and infrastructure mapping.
🛠 Infrastructure Mapping
Level 2 should ideally map to actual infrastructure components:
- Web App/Mobile App: Maps to a build artifact or deployment.
- API/Service: Maps to a Docker container or K8s deployment.
- Database: Maps to a managed cloud DB or persistent container.
- Message Broker: Maps to Kafka, RabbitMQ, or Pub/Sub.
🚫 Anti-Patterns to Guard (Level 2)
- NOT A FLOWCHART: Avoid modeling complex business logic; use a sequence diagram for that.
- NO LIBRARIES: Shared libraries (DLL, JAR, NuGet) are NOT containers.
More from kinhluan/skills
ddd-tactical
Tactical Domain-Driven Design (DDD) with Scoring Rubric. Use this skill when designing internal domain models or performing architectural reviews to ensure domain logic is isolated and rich.
7scheduling-algorithms
Job scheduling algorithms for parallel and distributed systems
7ddd-core
Professional Strategic Domain-Driven Design (DDD) Hub. Use this skill for Event Storming, identifying Subdomains, defining Bounded Contexts, and mapping Domain Models to the heart of your architecture.
6c4-level3-component
Specialized in Component diagrams (Level 3) with folder structure mapping. Use this skill when the user needs to zoom into a single container to identify internal components, their responsibilities, and how they map to actual code folders (src/services, internal/).
6security-analysis
Security vulnerability analysis and auditing procedures
6docker-containerization
Docker containerization best practices and patterns
6