- product-portfolio
- ecosystem-catalog
- deep-dives
- core
Cloud Infrastructure, SRE, Observability & Runtime - Analysis¶
Planning-layer analysis for category 9. It groups the 50 candidate services into capabilities, recommends what becomes a standalone service versus a module, and captures domain, interface, and non-functional notes. For the plain item list see the browse page.
Scope & Bounded Context¶
- Primary bounded context: Infrastructure & SRE
- Group: core
- Default wave / cycle: Phase 1 · Core Platform Wave
- Items: 50 candidates
This category is anchored to the ConnectSoft DDD baseline in the SaaS framework DDD blueprint and the service classification model.
Classification Breakdown¶
| Classification | Count |
|---|---|
| Microservice | 5 |
| Module-in-service | 41 |
| Platform Product | 3 |
| Portal/UI Module | 1 |
Anti-fragmentation stance
Per ADR-0011, the 41 module candidates below are delivered inside the Infrastructure & SRE bounded-context service, not as separate microservices. Only the 8 platform/service candidates justify an independent runtime.
Standalone Service / Platform Candidates¶
| ID | Service | Tier | Status |
|---|---|---|---|
| CS-SVC-0401 | Environment Provisioning Service | 1 | Planned |
| CS-SVC-0410 | Namespace Provisioning Service | 1 | Planned |
| CS-SVC-0416 | Service Mesh Control Service | 1 | Planned |
| CS-SVC-0431 | Business Continuity Service | 1 | Planned |
| CS-SVC-0441 | Log Platform | 1 | Planned |
| CS-SVC-0442 | Metrics Platform | 1 | Planned |
| CS-SVC-0449 | Chaos Engineering Service | 1 | Planned |
| CS-SVC-0450 | Platform Reliability Scorecard | 1 | Planned |
Portal / UI Modules¶
- APM Dashboard (
CS-SVC-0447)
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the Infrastructure & SRE context; cross-context reads go through published contracts, never shared databases.
- Integration is event-first (outbox + integration events) per the event-driven mindset.
- APIs are contract-first and versioned through the API & Integration context.
Non-Functional Posture¶
- Multi-tenancy & edition-awareness: required for all serious candidates.
- Security: Standard baseline; secrets via the platform secret store; least privilege.
- Compliance: standard audit logging.
- Observability: OpenTelemetry traces, metrics, and structured logs.
MVP vs Future¶
- MVP (Tier 0-1): Environment Provisioning Service, Environment Promotion Service, Environment Drift Monitor, Infrastructure Catalog, Infrastructure Blueprint Registry, IaC Module Registry, Pulumi Stack Management Service, Terraform State Management Service
- Future (Tier 4-5): none
Open Questions¶
- Which module candidates, if any, develop independent scaling or ownership needs that would justify promotion to a standalone service?
- Where do this category's contracts overlap with adjacent contexts, and who owns them?