- product-portfolio
- ecosystem-catalog
- deep-dives
- core
Developer Experience, SDLC, QA & Software Factory - Analysis¶
Planning-layer analysis for category 10. 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: Developer Factory
- Group: core
- Default wave / cycle: Phase 2 · Cycle 1: AI Factory SaaS
- 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 | 3 |
| Module-in-service | 42 |
| Platform Product | 2 |
| Portal/UI Module | 2 |
| Workflow Template | 1 |
Anti-fragmentation stance
Per ADR-0011, the 42 module candidates below are delivered inside the Developer Factory bounded-context service, not as separate microservices. Only the 5 platform/service candidates justify an independent runtime.
Standalone Service / Platform Candidates¶
| ID | Service | Tier | Status |
|---|---|---|---|
| CS-SVC-0452 | Internal Platform Portal | 1 | Planned |
| CS-SVC-0459 | Package Registry Service | 1 | Planned |
| CS-SVC-0461 | Container Registry Management | 1 | Planned |
| CS-SVC-0484 | Mock Server Service | 1 | Planned |
| CS-SVC-0500 | Software Factory Control Tower | 1 | Documented |
Portal / UI Modules¶
- Developer Portal (
CS-SVC-0451) - Engineering Metrics Dashboard (
CS-SVC-0489)
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the Developer Factory 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): Developer Portal, Internal Platform Portal, Service Catalog, Software Catalog, Golden Path Template Registry, Project Scaffolding Service, Repository Creation Service, Monorepo 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?