Requirements

Functional Requirements:

• Allow reservation of a parking spot.
• Process payment for the reservation.
• Enable parking of a car in the reserved spot.
• Support early departure before reservation time expires.
• Gate check-in/out.
• Handle no show.

Non-Functional Requirements:

List the key non-functional requirements (eg low latency, scalability, reliability, etc.)...

Capacity Estimation

Estimate the scale of the system. Consider daily active users, read/write ratio, storage requirements, bandwidth, and any relevant QPS calculations...

API Design

User Auth API:

• POST: Register
  • User ID
  • Name
  • Surname
  • Licence plate
  • email
  • password

Payment API:

• third-party like Auth0 for reserving funds, store card details and canceling reservations

Reservation API:

• POST: Create Reservation
  • Reservation ID
  • Start date
  • End date
  • Licence plate
  • Lot space number
• UPDATE: Update Reservation
  • Reservation ID
  • Start date
  • End date
  • Lot space number
• POST: Rancel reservation
  • Reservation ID

Billing API:

• GET: list of transactions and bills

Car movement API

• Post: Car Enter
  • Licence plate
• Post: Car Exit
  • Licence plate

High-Level Design

Two flows: for reservation management via app and car movement in the lot.

Vehicle movement service manages enter and exit of car. Reservation servce creates reservation and updates the take space in the lot. Space manager assigns the best spot for the car. Load balancers makes sure if in the event of concerts or matches many customers try to reques the spot, system can still process.

Database Design

simple SQL with tables for Users, Lot spaces, Reservations and bills.

Detailed Component Design

Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.