ifixkart-admin/docs/adr/ADR-006-events.md
Adithiyan bbd3a3e959 feat: initial commit — full platform snapshot
- Backend: FastAPI app with all models, services, schemas, routes
- Admin Panel: Next.js dashboard with all modules
  (CRM, POS, repairs, warranties, billing, notifications, etc.)
- Ecommerce: storefront (submodule) + product catalog
- AI Agents: .agents/ skill library for Antigravity IDE
- Docs: architecture, billing, notification gateway markdown
- Submodules: Backend/OpenWA, Ecommerce/File 2/storefront
2026-10-13 12:59:47 +05:30

7 lines
475 B
Markdown

# ADR-006: Transactional Outbox & Event Ordering
## Context
Decoupling database mutations from search/cache projections requires eventual consistency without data loss or race conditions.
## Decision
Implement the **Transactional Outbox Pattern** in MySQL. Every business mutation writes an outbox record (`aggregate_id`, `aggregate_version`). Celery workers dispatch events via RabbitMQ. Consumers enforce `aggregate_version` guards to discard stale, out-of-order events.