- product-portfolio
- ecosystem-catalog
- deep-dives
- vertical
Media, Content, Communications & Creator Economy - Analysis¶
Planning-layer analysis for category 24. 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: Media & Content
- Group: vertical
- Default wave / cycle: Phase 5 · Cycle 5: Marketplace & Ecosystem
- 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 |
|---|---|
| Module-in-service | 39 |
| Platform Product | 4 |
| Portal/UI Module | 3 |
| Workflow Template | 4 |
Anti-fragmentation stance
Per ADR-0011, the 39 module candidates below are delivered inside the Media & Content bounded-context service, not as separate microservices. Only the 4 platform/service candidates justify an independent runtime.
Standalone Service / Platform Candidates¶
| ID | Service | Tier | Status |
|---|---|---|---|
| CS-SVC-1151 | Content Management System | 4 | Documented |
| CS-SVC-1163 | Video Streaming Platform | 4 | Planned |
| CS-SVC-1179 | Community Management Platform | 4 | Planned |
| CS-SVC-1199 | Communications Command Center | 4 | Planned |
Portal / UI Modules¶
- Membership Content Portal (
CS-SVC-1167) - Content Performance Dashboard (
CS-SVC-1183) - Brand Portal (
CS-SVC-1196)
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the Media & Content 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): see roadmap
- Future (Tier 4-5): Content Management System, Headless CMS API, Content Publishing Service, Editorial Workflow Service, Content Calendar Service, Media Asset Library, Digital Asset Management, Image Transformation Service
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?