How rahulsahofficial/lld works
Project type and purpose
• This repo is a teaching/learning workspace covering:
• Design Patterns demos (Strategy, Factory, Singleton, etc.)
• OOP experiments
• SOLID principles code
• Two small applications:
– GoogleDoc editor (Projects/GoogleDoc)
– BrOla ride‐sharing hackathon (Hackathon/BrOla)
• Of these, the BrOla folder represents a coherent mini‐application with multiple cooperating modules.
File structure
• Top‐level folders each represent independent domains.
• Drill into Hackathon/BrOla:
• Models/ — domain entities (Driver, Rider, Ride, Vehicle, User)
• Managers/ — in‐memory state managers (DriverManager, RiderManager, RideManager)
• Services/ — functional modules:
– DriverAssignService
– PricingService
– VehiclePricingService
– PaymentService (+ factory & strategies)
– NotificationService (SMS, App)
– OtpService
• Utils/ and Types/ — shared types (e.g. Location, Types.h)
• main.cpp — orchestrates end‐to‐end flow
• Outputs/ — sample run logs
Extract insights from README
• “BrOla” implements ride‐request, assignment, pricing, payment and notifications using Strategy and Factory patterns.
• The code emphasizes separation of concerns via interfaces and service classes.
a. Main components
• Clients (Rider App / CLI)
• RideManager (handles ride requests)
• DriverAssignService (matches riders & drivers)
• PricingService & VehiclePricingService (compute fare)
• PaymentService (+ PaymentServiceFactory + strategies)
• NotificationService (+ SMS & App channels)
• OtpService (for authentication)
• Data stores (in this demo, in‐memory Managers)
• Domain Models (Driver, Rider, Ride, Vehicle)
b. Relationships & interactions
1. Rider sends “requestRide” → RideManager
2. RideManager → DriverAssignService → selects Driver via DriverManager
3. RideManager → PricingService & VehiclePricingService → calculate fare
4. Rider confirms → PaymentServiceFactory produces chosen PaymentStrategy (UPI/COD) → processPayment
5. On success/failure → NotificationService notifies via SMS or In‐App
6. Optionally, OtpService invoked for verification
7. RideManager creates Ride model, updates RideManager state
c. Architectural patterns & principles
• Strategy (Payment, Notification, Vehicle pricing)
• Factory (PaymentServiceFactory)
• Single Responsibility (each service does one thing)
• Dependency Injection (services interact via interfaces)
d. Key technologies & libraries
• Plain C++ classes & headers
• No external DB: in‐memory managers
• Console‐based I/O (main.cpp demonstrating flows)