Architecture and domain boundaries
Understand service responsibilities and commerce authority.
On this page
Service responsibilities
| Component | Responsibility |
|---|---|
| Rust gateway | Authentication, domain operations and receipts. |
| PostgreSQL | Transactional records, constraints and migrations. |
| Admin/storefront | Typed operational and shopping interfaces. |
| Node renderer | Public documents from approved snapshots. |
| Python assistant | Orchestration through scoped capabilities. |
| Node language engine | Supported interpretation contracts. |
| Workers | Search, reporting, exports and asynchronous work. |
Plan for synchronous and asynchronous state
- Commerce transactions own related writes and reservations.
- Search and reporting are derived, asynchronous views.
- Published snapshots remain separate from revisioned drafts.
- Availability subtracts live holds, independently of cleanup backlog.
- Monitor worker tasks and dependency health.
Design integrations around contracts
Use supported APIs and preserve required revisions/replay keys. Keep business validation in its owning domain.
Each client has an independent database and configuration. Channels, themes and stock pools do not provide client isolation.