EP-CORE-ARCH: Core Technical Architecture¶
Scope¶
Foundational platform: service boundary design, messaging backbone, SPA/PWA shell, tenant isolation strategy.
Requirements (Stories / Arch Tasks)¶
- REQ-131 Define initial service boundaries (auth, tenant, billing, HR gateway)
- REQ-132 Implement async messaging adapter (Kafka/RabbitMQ abstraction)
- REQ-133 Deliver SPA/PWA shell with offline manifest
- REQ-134 Enforce tenant isolation patterns (schema or row-level security decision)
Dependencies¶
None (foundation). Enables all other epics.
NFR Touchpoints¶
- Scalability: horizontal service replicas stateless core
- Security: isolation stress tests; secrets management
- Observability: central tracing & correlation IDs across messages
- Performance: baseline latency budgets per service
Success Metrics¶
- p95 inter-service request latency < 250ms baseline
- Multi-tenant isolation test suite pass rate 100%
- Message delivery success (>99.9%) for critical events
Risks & Mitigations¶
| Risk | Mitigation |
|---|---|
| Over-engineering microservices | Start with modular monolith; split by clear SLA breaches |
| Messaging complexity & retries | Implement idempotent consumers + dead-letter queue |
| Tenant isolation misconfiguration | Automated regression tests + linting rule for tenant filters |
Rollout Strategy¶
Phase 1: Modular monolith boundaries + async facade. Phase 2: Extract auth & document services. Phase 3: Introduce full tracing & tenant isolation audits.
Version: 1.0