VrhamanArchitecture

Vrhaman is a full-stack mobility platform built to streamline vehicle rentals across customer booking, vendor fulfillment, and admin governance—transactional APIs, real-time coordination, and role-specific apps for speed, visibility, and reliability.

This narrative covers intent, architecture, engineering decisions, operations, and the path to portfolio-grade, enterprise-ready delivery.

Traditional rental operations often fail at coordination and operational visibility:

• Booking processes are slow and fragmented
• Vendor response cycles are inconsistent
• Customers lack transparent status visibility
• Admin teams lack a single control plane for lifecycle performance
• Payments, notifications, and operations sit in siloed tools

Vrhaman closes these gaps with one coordinated digital system.

Vrhaman is designed to deliver:

• Fast, predictable booking
• Real-time customer ↔ vendor communication
• Operational traceability for admins
• Trust-building public web for acquisition
• Scalable multi-city operations

Surfaces inferred from backend routers/controllers—names follow repository conventions.

Eight-step lifecycle from discovery to admin oversight.

Token-authenticated sockets, role-aware channels, and reconnect-aware delivery are the product differentiator.

• Token-authenticated socket sessions
• Separate registration channels for customer and vendor sockets
• Persistent socket-connection mapping (`socket_connections`)
• Reconnect-aware state restoration (latest booking pushed on reconnect)
• Status-specific event types (`accepted`, `rejected`, `cancelled`, `update`)
• Timer-aware handling for payment confirmation windows

Business impact

• Lower customer uncertainty
• Faster vendor response loops
• Better lifecycle transparency without manual polling

• Reconnect-safe real-time synchronization for both user roles
• Duplicate or stale socket registration avoidance
• Token expiry handling in mobile app sessions
• Cross-channel notification consistency (socket + push)
• Time-sensitive booking transitions (e.g., payment confirmation windows)
• Connectivity-aware UX fallback for unstable networks

Implemented

• JWT-based API authentication
• Authenticated socket handshake
• Role-aware route segregation
• Token/session expiry handling in mobile flows

Recommended hardening

• API rate limiting and abuse protection
• Upload validation and secure media processing
• Secret isolation policy across environments
• Payment callback verification guardrails
• Structured audit trails for admin-critical actions

• Keep APIs stateless for horizontal scaling
• Expand Redis strategy for caching/event coordination
• Introduce queue-based async handling for notifications/heavy workflows
• Add socket scaling strategy (adapter/pub-sub model)
• Define index strategy for booking-heavy collections
• Optimize media delivery with CDN-backed assets

Why separate customer and vendor apps?

• Focused UX for distinct intents
• Operational isolation and simpler workflows
• Better notification targeting
• Independent release cadence

Why Socket.IO over polling?

• Lower interaction latency
• Event-driven booking lifecycle UX
• Less load at high booking activity
• Cleaner status-sensitive workflows

• Booking as the central transactional entity
• User, vendor, and vehicle linked through booking relationships
• Persistent socket session mapping for targeting
• Support collections: coupons, wishlist, reviews, documents
• Indexing: booking status/time, vendor/customer lookup, active lifecycle queries

Document per-environment behavior: dev, staging, prod, release and rollback, monitoring for API and socket health, CI/CD for backend and mobile builds, and infra anchors (compute, MongoDB host, Firebase, S3).

Tune this list for interviews and portfolio accuracy.

Same systems we ship in production—shown here as icon clusters (hover or focus for names).

Quantified outcomes matter most for investors and enterprise buyers—swap templates for live numbers.

Metrics to instrument

• Daily and monthly bookings
• Average vendor response time
• Booking confirmation time
• Socket event delivery latency
• Payment success rate
• Onboarding completion rate
• Active vendors by city
• Repeat customer rate
• Cancellation rate reduction

Impact statement templates

• “Real-time event coordination reduced average booking confirmation delay from X min to Y sec.”
• “Vendor response SLA compliance improved from A% to B%.”
• “Customer cancellation due to delayed confirmation dropped by N%.”

Reserved frames for admin, customer, vendor, marketing, observability, and mobile onboarding. Export at 2× for crisp portfolios.

Early validation themes from real riders.

Feedback themes

• Service quality and professionalism
• Smooth booking journey
• Strong support perception
• Clear onboarding

Vrhaman is a coordinated platform—not a single app—with integrated customer, vendor, admin, and real-time layers. The foundation supports portfolio-grade storytelling once metrics and visuals land.