Event-driven, domain-driven, 100% serverless architecture designed for global scale and reliability
Six-layer architecture from frontend to infrastructure
Domain-driven design with clear service boundaries
auth-svc, user-svc, team-svc, tenant-svc
event-svc, venue-svc, tour-svc, calendar-svc
marketplace-svc, wallet-svc, payment-svc, orders-svc
llm-orch-svc, aibrain-svc, cypher-svc, studio-svc, rag-svc, mcp-svc, eventml-svc
notify-svc, chat-svc, inbox-svc, integration-hub-svc, whatsapp-svc
cms-svc, webify-svc, sphere-svc, vault-svc, taxonomy-svc
analytics-svc, reports-svc, search-svc, reviews-svc, rewards-svc
portal-registry-svc, domains-svc, subscriptions-svc, billing-svc, support-svc, status-svc
Battle-tested patterns for enterprise reliability
Services communicate via Kafka events, not direct HTTP calls. Prevents circular dependencies, enables async workflows.
Single entry point for all client requests. Routes to appropriate service, handles auth, rate limiting, logging.
Each service owns its data. No shared databases. Multi-tenant isolation via Row-Level Security (RLS).
Transactional outbox ensures database writes and event publishing are atomic. Prevents data inconsistency.