Artistry Cart
PROJECT
OVERVIEW
A production-oriented, multi-vendor commerce platform built as an Nx monorepo. The architecture deliberately sits between a monolith and a fully decoupled microservices system — 9 deployable applications share a unified Prisma schema on MongoDB while maintaining logical service boundaries through code ownership, dedicated ports, and an API gateway routing layer.
Multi-vendor artisan commerce built as a service-oriented Nx monorepo. 9 deployable applications connected through an API gateway, Kafka event streaming, and shared infrastructure packages — with AI Vision fully isolated from transactional commerce.
“A practical middle ground between a pure monolith and a fully decoupled distributed system — service boundaries are logical rather than physical, which is the right tradeoff for a solo-operated platform.”
SYSTEM
ARCHITECTURE
Engineered for production durability, type safety, and scalable domain isolation. Every module operates with strict boundaries and predictable failure handling.
MODULAR DOMAIN ISOLATION — BUILT FOR ZERO-DOWNTIME DEPLOYMENTS, TYPE-SAFE CONTRACTS, AND FAIL-SAFE EXCEPTION BOUNDARIES.
PROJECT
IMPACT
Production performance measured under live traffic load, latency stress profiles, and automated system profiling.
ALL OUTCOMES ARE EMPIRICALLY VERIFIED IN PRODUCTION ENVIRONMENTS — MEASURED UNDER HIGH CONCURRENCY, PEAK LATENCY PROFILES, AND AUTOMATED SYSTEM HEALTH AUDITS.
Deployable Apps
Database Models
CI/CD Workflows
Architecture Decision Records
KEY
CAPABILITIES
Core capabilities engineered for high-scale reliability, intuitive operator workflows, and real-time production execution.
PRODUCTION-TESTED SYSTEM FEATURES — ARCHITECTED FOR LOW-LATENCY INTERACTION, DETERMINISTIC STATE HANDLING, AND COMPREHENSIVE TELEMETRY.
Service-Oriented Nx Monorepo
9 deployable applications (2 Next.js frontends, 1 API gateway, 5 domain services, 1 Kafka worker) and 5 shared infrastructure packages. Nx affected builds skip unchanged services, and shared TypeScript config ensures consistency.
Kafka Analytics Pipeline with DLQ
Frontend publishes user activity events (browse, cart, wishlist, shop visits) to Kafka. Order-service publishes purchase events via an outbox pattern. The kafka-service worker materializes these into UserAnalytics, productAnalytics, and shopAnalytics read models with manual offset commits and dead-letter queue support.
AI Vision Service Boundary
Isolated service handling text/image generation via Gemini, visual search via CLIP embeddings, concept galleries, artisan matching, and scheduled maintenance via Agenda.js. Supports anonymous exploration on selected paths while enforcing auth on creation routes.
Stripe Connect with Webhook Verification
Handles payment sessions and intents for checkout, with 90/10 seller/platform fee splitting. Stripe webhooks mount before JSON body parsing to preserve raw request body for signature verification — a subtle but critical ordering requirement.
CI/CD Pipeline with Security Scanning
5 GitHub Actions workflows: PR validation with Nx affected tests/builds, image publishing to GHCR with Trivy scanning and SBOM/provenance, staging deployment via Kustomize overlays, controlled production promotion, and nightly security audits.
DEVELOPMENT
PROCESS
A rigorous, phased engineering lifecycle designed to transform architectural requirements into scalable, production-ready systems.
DISCIPLINED SYSTEM METHODOLOGY — ARCHITECTED FOR END-TO-END OBSERVABILITY, DETERMINISTIC REVIEWS, AND ZERO-REGRESSION RELEASE CYCLES.
TECHNOLOGY
STACK
An engineered architectural map outlining foundational nodes, runtime environments, and type-safe deployment frameworks.
DETERMINISTIC ARCHITECTURE STACK — PROFILED FOR PRODUCTION LATENCY, STRICT TYPE SAFETY, AND HIGH-CONCURRENCY SCALABILITY.