- product-portfolio
- ecosystem-catalog
- deep-dives
- core
Configuration, Feature Flags, Entitlements & Policy - Analysis¶
Planning-layer analysis for category 3. 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: Config & Feature Flags
- 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 | 4 |
| Module-in-service | 44 |
| Shared Library | 1 |
| Workflow Template | 1 |
Anti-fragmentation stance
Per ADR-0011, the 44 module candidates below are delivered inside the Config & Feature Flags 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-0101 | Configuration Server | 0 | Live |
| CS-SVC-0124 | Server-Side Flag Evaluator | 0 | Planned |
| CS-SVC-0129 | Runtime Policy Engine | 0 | Planned |
| CS-SVC-0130 | Business Rules Engine | 0 | Planned |
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the Config & Feature Flags 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: High 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): Configuration Server, Centralized App Settings Service, Tenant Configuration Service, Environment Configuration Service, Secret Reference Configuration Service, Dynamic Configuration Reload Service, Configuration Versioning Service, Configuration Approval Workflow
- 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?