Application Design & Tech Stack
CXOS — Customer Experience Operating System
Unified. Real-time. AI-Native. Built for the Future. This reference walks through the six-stage architecture that takes an event from a customer touchpoint all the way to real-time activation.
Architecture at a Glance
Full end-to-end diagram — click to zoom.
Source diagram: doc/img/cxos-architecture.jpeg
The Six Modules
Each stage below drills down into its own reference page with submodules and a real-world example.
Data Sources
Every customer touchpoint, business system, and file feed that produces raw events.
Ingestion Layer
SDKs, edge network, and connectors that collect, validate, and route events in real time.
Transformation & Processing
Stream and batch processing that dedupes, stitches identity, and models data for use.
Unified Data Foundation
The CXOS Data Lakehouse — one copy of data, open formats, full governance.
Intelligence & Services
Identity, query, AI, and operational services layered on top of the foundation.
Destinations & Activation
Real-time and batch delivery to the platforms where customer experience happens.
End-to-End Flow (Example)
How a single product-view event travels through this reference implementation's stack — Angular, .NET Core, and PostgreSQL.
A customer views a product on the Angular storefront. Angular POSTs a ProductViewed event to a .NET Core Web API ingestion endpoint. A .NET Core worker service (IHostedService) reads the event off a queue, deduplicates and enriches it, and persists it to PostgreSQL as the system of record. A .NET Core analytics API queries PostgreSQL (materialized views / window functions) to compute a propensity score, and the resulting insight triggers a .NET Core notification service that sends a personalized activation email.
Cross-Cutting Foundation
Capabilities that run underneath every module above.
Observability
Logs, Metrics, Traces
Security
IAM, Secrets, Threat Detection
Developer Platform
APIs, SDKs, Docs, Sandboxes
Multi-Tenancy
Isolation, Quotas, Limits
Administration
Users, Roles, Audit, Settings
Key Design Principles
- Collect once, use everywhere
- Real-time by default
- Metadata drives everything
- Open, extensible, and future-proof
- Privacy, security, and governance baked-in
- Built for scale and performance
Legend
- Data Flow (Real-time)
- Data Flow (Batch / Near Real-time)
- Control / Metadata Flow