PixelWibes

Schedule a Free Call

SAC Modernization Project

Architectural Vision: Transitioning from a Regional Monolith to a Global, Event-Driven, Al-Enabled SaaS Platform.

Enterprise Modernization

Cloud Transformation

Digital Innovation

Executive Summary

CURRENT STATE

Decentralized Databases

Fragmented data sources across regions causing synchronization issues.

Monolithic Legacy App

Difficult to scale high-load services independently.

Development Bottlenecks

Manual testing and frequent code conflicts between regional teams.

TARGET STATE

Cloud-Native Microservices

Domain-driven architecture utilizing Polyglot Persistence.

Real-Time Processing

Stream processing for immediate theft detection via GPS.

Gen Al Support

Revolutionizing customer support with Al-driven resolutions.

Strategic Business Value

Global Scalability

Support expansion beyond the current IO cities with decoupled architecture.

Operational Efficiency

Automate theft detection and support ticket resolution.

Developer Velocity

Eliminate code overwrites through a modern CI/CD pipeline.

High-Level System Architecture

Domain-Driven Microservices

Transitioning from a monolithic structure to independent, domain-driven services to ensure resilience and agility.

Decomposition & Decoupling

High-load services (Tracking) are isolated from critical transactional services (Payments) to prevent cascading failures.

Independent Scalability

Scale Telemetry ingestion to 100+ instances for GPS load without paying for unnecessary Billing instances.

Event-Driven Design

Moving from batch to real-time. Services communicate asynchronously via Kafka events.

Polyglot Persistence

Using the right tool for the job: Relational for payments, Time-Series for GPS, Graph for fleet logic.

Core Services Breakdown

Identity & Access

Handles Rider registration, Real-time Drivers License verification, and RBAC for 4 employee types.

Fleet Inventory

Manages the status (Active, Maintenance, Stolen) Of the entire fleet Of 4,000 cars.

Pricing Engine

Calculates dynamic costs based on demand and schedules bookings efficiently.

Telemetry

Handled by AI across all channels simultaneously

Support Al

The "Vibe Coding- layer for Chat automation and RAG- based support insights.

Why this approach? Strategic Benefits

Fault Isolation & Decoupling

Critical transactional services are protected. If the Pricing System goes down, users can Still unlock cars they have already booked.

Independent Scalability

We can scale the Telemetry Service to 100 instances to handle GPS load spikes without paying for 100 instances of the Billing Service.

Core vs. Edge Repository Strategy

THE PROBLEM

0 Teams frequently overwrite each other's code" and "Local support teams cannot fix other regions' code" due to a monolithic repository.

The Solution: Polyrepo Structure

sac -core- platform

Repo A

Contains *Immutable" logic: Identity, Payments, Car Locking.

Write: Core Team Only (Regions Read-Only)

sac region - plugins

Repo B, C, D

Region-specific logic: Tax rules, IJI languages, Local laws.

Write: Local Regional Teams

Enforcement: Core code is protected. Regions extend functionality only via strict APIs or "Plugin" patterns.

Branching & Automated Pipeline

The CIICD Gatekeeper

Automated pipeline running on every pull Request (PR).

Lint & Al Unit Tests

"Vibe Coding' Al tools generate unit tests. Code quality is enforced automatically.

Must pass 100% to merge

Integration Testing

ploys microservice to ephemeral containers to validate service-to-service contracts.

Validates API schema & connectivity

Blue/Green Deployment

Deploy to "Blue' env first. If metrics look good, switch traffic, Prevents "bugs in Prod".

OUTCOME

Prevents Overwrites

OUTCOME

Auto QA Gates

Data Strategy: Polyglot Persistence

An example alert with an Strategy: Moving away from "One DB for everything" to choosing the right tool for the specific workload.

DATA DOMAIN	DATABASE CHOICE	TYPE	STRATEGIC RATIONALE
User & Financial Payments, Profiles	PostgreSQL	Relational (ACID)	Requires strict ACID compliance. we cannot lose payment data or tolerate "half-registered" users inconsistent states.
Car GPS Telemetry Location History, Logs	Cassandra / DynamoDB	NoSQL / Tie-Series	Handles massive write volume (4,000 cars x 2 updates/min). Relational DBs would choke on this high-throughput log data.
Fleet Connectivity Rebalancing, Logistics	Ne04j	Graph DB	Optimizes •rebalancing". Instantly answers complex spatial queries: •Which tow truck is closest to Car A and Repair Shop?•
Support Knowledge RAG, Semantic Search	Pinecone / Weaviate	Vector DB	Enables Al RAG system to search manuals and chat logs by semantic meaning" rather than just keyword matching.

Data Strategy: Polyglot Persistence

Ultra-Low Latency

educes detection time from immediate response prevents vehicle loss.

System Resilience Kafka acts a nprqi«tpn

Prevents OverwritesKafka acts as a persistent buffer. Even if the Database goes down, theft detection remains active and no data is lost.

AI & Support Modernization

THE "AI SIDECAR" STRATEGY Augmenting human capabilities with Generative AI and automated insights.

Agent Assist

RAG Architecture

Eliminates manual search time. The system retrieves context from the Vector DB (Manuals + Past Tickets) to instantly draft accurate responses for agents.

Search by semantic meaning
Unified Knowledge Base

Sentiment Analysis

proactive Insights

Background workers analyze chat logs to automatically tag "Angry Users" for priority handling and surface "Trending Defects" to the Executive Dashboard.

Real-time churn prevention
Identify defects before reports

Code Generationa

Dev Velocity

Developers leverage Cursor/Copilot to generate boilerplate code for new regional features, significantly speeding up the rollout to US & Global markets.