- product-portfolio
- ecosystem-catalog
- deep-dives
- horizontal
Digital Marketing, MarTech, AdTech & Growth - Analysis¶
Planning-layer analysis for category 13. 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: Marketing & Growth
- Group: horizontal
- Default wave / cycle: Phase 3 · Cycle 2: Horizontal 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 | 1 |
| Module-in-service | 38 |
| Platform Product | 9 |
| Portal/UI Module | 1 |
| Workflow Template | 1 |
Anti-fragmentation stance
Per ADR-0011, the 38 module candidates below are delivered inside the Marketing & Growth bounded-context service, not as separate microservices. Only the 10 platform/service candidates justify an independent runtime.
Standalone Service / Platform Candidates¶
| ID | Service | Tier | Status |
|---|---|---|---|
| CS-SVC-0601 | Digital Marketing Command Center | 2 | Documented |
| CS-SVC-0602 | Omnichannel Campaign Platform | 2 | Documented |
| CS-SVC-0604 | Paid Ads Management Platform | 2 | Documented |
| CS-SVC-0613 | Ad Spend Allocation Engine | 2 | Planned |
| CS-SVC-0625 | Marketing Attribution Platform | 2 | Planned |
| CS-SVC-0635 | Audience Segmentation Platform | 2 | Planned |
| CS-SVC-0638 | Customer Data Platform | 2 | Planned |
| CS-SVC-0644 | Newsletter Platform | 2 | Planned |
| CS-SVC-0647 | SEO Management Platform | 2 | Planned |
| CS-SVC-0649 | Reputation Management Platform | 2 | Planned |
Portal / UI Modules¶
- Campaign Planning Calendar (
CS-SVC-0603)
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the Marketing & Growth 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): Session Replay Service, Identity Resolution 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?