27 lines
930 B
Markdown
27 lines
930 B
Markdown
# Architecture & APIs
|
||
|
||
Status: draft
|
||
Owners: Architecture
|
||
|
||
Overview
|
||
- Modular, domain‑driven architecture with clear boundaries and open APIs.
|
||
|
||
Modules
|
||
- Identity & Profiles, Forum, Content (Blog/Resources), Media (Podcast), Tribute, Commerce, Compliance, Platform (Design System + Apps), Integration.
|
||
|
||
Client platforms
|
||
- Mobile: Android/iOS (proposed: React Native/Expo or Flutter — to be decided via proposal)
|
||
- Web: Next.js/SSR or Flutter Web — parity is mandatory and defined per feature spec
|
||
|
||
Backend
|
||
- Proposed: API service with OpenAPI, Postgres primary store, object storage for media, search index for forum/content, queue for async tasks.
|
||
|
||
API standards
|
||
- REST+JSON with OpenAPI; WebSocket for realtime forum/presence; OAuth2/OIDC; rate limits; pagination; idempotency keys.
|
||
|
||
Data boundaries
|
||
- Strict separation of PHI/PII domains; audit and consent services.
|
||
|
||
Decisions
|
||
- <record cross‑cutting decisions here>
|
||
|