Skip to content
  • product-portfolio
  • ecosystem-catalog
  • deep-dives
  • packs

Cross-Industry Vertical Templates & Solution Packs - Analysis

Planning-layer analysis for category 29. 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: Vertical Solution Packs
  • Group: packs
  • Default wave / cycle: Phase 4 · Cycle 4: AI Interaction & Verticals
  • 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
Vertical Solution Pack 50

Anti-fragmentation stance

Per ADR-0011, the 0 module candidates below are delivered inside the Vertical Solution Packs bounded-context service, not as separate microservices. Only the 0 platform/service candidates justify an independent runtime.

Standalone Service / Platform Candidates

None - this category is delivered through modules, packs, or shared runtimes.

Domain, Interfaces & Data Ownership

  • Aggregates are owned by the Vertical Solution Packs 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): Subscription Billing Solution Pack
  • 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?