Skip to content

SaaS Solution Platform — Architecture Blueprint

Enterprise Architecture Objectives

The SaaS Solution Platform provides the structural model for multi-bounded-context SaaS products: DDD-aligned services, template-driven repositories, contract-first APIs, and a composable Blazor front end. This blueprint aligns with ConnectSoft principles: Clean Architecture, cloud-native deployment, observability-first, security-first.

Architectural Principles

  1. One deployable service per bounded context (per generated solution from a ConnectSoft.Saas.*Template).
  2. Anti-corruption at context boundaries — identifiers and integration events only.
  3. ServiceModel is the only consumer-facing contract surface for HTTP/gRPC clients.
  4. BaseTemplate submodule — shared kernel without domain; no fork of “MicroserviceTemplate.Base” branding in SaaS naming.
  5. Phase libraries — ConnectSoft.Extensions.Saas.* extracted after templates prove structure.

Context Map (Logical)

flowchart LR
  subgraph core [Core SaaS contexts]
    T[Tenants]
    P[ProductCatalog]
    E[Entitlements]
    B[Billing]
    M[Metering]
  end
  subgraph foundation [Foundation platforms]
    IdP[Identity Auth]
    GW[API_Gateway]
    CFG[Config_Platform]
  end
  subgraph ux [Experience]
    Shell[Blazor_Shell_Saas]
    MFE[MFE_modules]
  end
  T --> P
  P --> E
  E --> B
  P --> M
  core --> IdP
  core --> GW
  Shell --> GW
  MFE --> GW
  Shell --> MFE
Hold "Alt" / "Option" to enable pan & zoom

Arrows indicate primary information or dependency direction; exact integration uses events and REST/gRPC as specified.

Layering (Reference)

Layer Artifacts
Experience ConnectSoft.Blazor.Shell.Saas, MFE template repos
Edge API Gateway, BFF policies
Application Use cases, orchestration inside each service
Domain Aggregates, domain events inside each context
Infrastructure Persistence, messaging, external APIs
Contracts ServiceModel, RestApi, Grpc packages

Relationship to Canonical Specs

Compliance and Governance

  • Tenant data — Isolation and residency follow product policy; cross-links to Audit Platform for tamper-evident logs where required.
  • Configuration — Non-domain toggles use Config Platform.

Enterprise Architect Checklist