MatchingComing soon
Route-Based Matching
Commuters are matched using recurring routes and schedules rather than an on-demand ride-hailing model.
System Design
Designing Practical, Scalable Systems
I use systems thinking to connect product goals with technical architecture. This includes understanding users, modeling data, designing services, and making trade-offs between simplicity, scalability, trust, and delivery speed.
Trusted Carpool Network
A verification-first commuter matching platform designed to improve trust and safety for daily commuters.
Product StrategyUser FlowsSystem ArchitecturePostgreSQL
Key Design Decisions
Explore the technical and product decisions that shaped the Commute Matcher platform.
Database
PostgreSQL over MongoDB
PostgreSQL was selected to support strongly related data, reliable matching logic, auditability, and transactional consistency.
Read the full decisionBooking Experience
Automatic Booking Instead of Driver Approval
Publishing a route is treated as a driver's pre-commitment, allowing eligible passengers to reserve available seats without waiting for manual approval.
Read the full decisionProduct Design
Verified Commuters Rather Than Open Ride Sharing
Commute Matcher prioritises a trusted network of identifiable commuters rather than allowing unrestricted participation from anonymous users.
Read the full decisionTrust & Safety
Verification-First Approach
Users must meet the required verification level before creating routes, booking seats, or joining confirmed commutes.
Read the full decisionDesign Artifacts
User Flow Diagram
Shows how riders and drivers move from registration to verification, ride creation, matching, booking, and confirmation.
User Flow Diagrams
These flows show how users register, select rides, book trips, and complete payment within the Trusted Carpool Network.
User Registration & Verification
Shows how users create an account, submit verification details, and become eligible to participate in trusted ride matching.
Select Ride Flow
Shows how a commuter searches available rides, reviews route details, and selects a suitable ride option.
Booking & Payment Flow
Shows how a rider books a selected ride, confirms trip details, and completes payment.
System Architecture
Shows how the frontend, authentication service, matching service, notification service, payment flow, and database communicate.
Entity Relationship Diagram
Shows the relational database structure for users, rides, bookings, payments, verification records, and driver profiles.
