Observability Standards
Operational metrics, audit logging, reporting, and infrastructure observability statements present in current docs.
Foundation services
Foundation services are shared platform capabilities used by multiple primitives.
Examples include:
- Notification service
- Settlement service
- Reconciliation service
- Audit and compliance service
- Configuration service
- Feature flag service
- Webhook service
- Reporting service
- Observability stack
Foundation services should be reusable across products and primitives.
Infrastructure layer
The infrastructure layer provides the runtime foundation.
It includes:
- Cloud infrastructure
- Databases
- Message bus
- Cache
- Object storage
- Secrets management
- KMS
- CI/CD
- Logging
- Metrics
- Tracing
- Alerting
Infrastructure should support strong isolation, auditability, observability, and reliable financial transaction processing.
Primitive design rules
Each primitive should:
- Own its domain
- Own its database
- Expose stable APIs
- Publish domain events
- Support idempotent commands
- Maintain audit logs
- Enforce authorization
- Support tenant-level configuration where needed
- Avoid direct database access from other services
- Avoid leaking provider-specific details into product APIs