SaaS Solution Platform — Integration Patterns¶
Identity and Access¶
- OIDC — Browser and MFEs authenticate against Authorization Server; access tokens presented to API Gateway.
- Service-to-service — Client credentials or on-behalf-of flows as standardized by platform security; tenant carried in claims and propagated headers.
See Identity Platform.
API Gateway¶
- Routing — Path or host-based routes to Tenants, Catalog, Entitlements, Billing, Metering services.
- Cross-cutting — Rate limits, auth, header propagation, redaction—per gateway template capabilities.
Configuration¶
- Feature flags and non-domain settings — Config Platform.
- Domain product data — Product catalog context, not Config.
Cross-Context Communication¶
| Pattern | Use when |
|---|---|
| Synchronous API | Read models, get operations needing immediate consistency |
| Integration event | After commit; Billing reacts to subscription changes, etc. |
| Saga / process manager | Multi-step workflows with compensations (document per flow) |
Rule: No direct database access across contexts; IDs and contracts only.
Notifications and Audit¶
- Notifications — Emit events consumed by Notifications Platform; SaaS contexts do not implement full notification infrastructure here.
- Audit — Forward audit-worthy actions to Audit Platform per compliance policy.