Omnichannel AI Platform — Aniket Thakur

The Problem

Managing customer communications across email, webchat, and messaging platforms creates duplicated logic and fragmented user profiles.

Engineering Approach

Constructed an enterprise-style monorepo with isolated API, background worker, contract packages, and strict schema validation.

What I Built & My Contribution

Built clean monorepo architecture, Fastify service boundaries, shared contract validation, Redis queue abstractions, and log redaction middleware.

Architecture & Data Pipeline

Web Clients → Fastify API Gateway → MySQL Persistence → Redis Queues → Private AI Worker

System Architecture

[ Web & Messaging Clients ]
            │
            ▼
┌───────────────────────────────┐
│      Fastify API Gateway      │
│   - Correlation ID & Logging  │
│   - Zod Contract Validation   │
└───────────────┬───────────────┘
                │
        ┌───────┴───────┐
        ▼               ▼
[ MySQL Database ]  [ Redis Queue ] ──► [ AI Worker Service ]

Verified Outcomes & Metrics

Strict monorepo package separation; schema-governed contracts; zero-leakage log sanitization.

Verified Implementation

The inspected API initializes health dependency checks, correlation IDs, schema negotiation, and personal data log redaction. Verification here represents code audit and local inspection, distinguishing functional code paths from external cloud provider accounts.

Boundaries & Known Limitations

Reference enterprise architecture foundation. Configured live external channel delivery and production readiness are not independently verified.