- product-portfolio
- ecosystem-catalog
- deep-dives
- marketplace
Marketplace, Ecosystem, App Store & Partner Platform - Analysis¶
Planning-layer analysis for category 28. 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: Marketplace & Ecosystem
- Group: marketplace
- 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 |
|---|---|
| Connector | 1 |
| Module-in-service | 41 |
| Platform Product | 1 |
| Portal/UI Module | 6 |
| Workflow Template | 1 |
Anti-fragmentation stance
Per ADR-0011, the 41 module candidates below are delivered inside the Marketplace & Ecosystem bounded-context service, not as separate microservices. Only the 1 platform/service candidates justify an independent runtime.
Standalone Service / Platform Candidates¶
| ID | Service | Tier | Status |
|---|---|---|---|
| CS-SVC-1400 | ConnectSoft Ecosystem Hub | 3 | Planned |
Connector Candidates¶
- Connector Marketplace (
CS-SVC-1354) - plugin in the Connector Runtime.
Portal / UI Modules¶
- Partner Portal (
CS-SVC-1356) - Third-Party Developer Portal (
CS-SVC-1381) - Developer Documentation Portal (
CS-SVC-1383) - Partner Support Portal (
CS-SVC-1391) - Marketplace Trust Center (
CS-SVC-1398) - Ecosystem Health Dashboard (
CS-SVC-1399)
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the Marketplace & Ecosystem 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): Partner Billing Service, Marketplace Billing Integration
- 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?