Loading...
vehicle entry/exit, parking space allocation, identify if spot occupied/free, payment management
scalability, availability, security,
should be able to handle anywhere from 700-1000 cars
POST - for car entry
GET - total car in lot
POST - for car exit
POST - for payment
have a car table, a spot table, place car in spots table, have a payment table
a simple server with reverse proxy should be able to manage traffic
car enters ticket is given
write made to db of ticket, to car liscence plate,
car parks
write made to spot table to identify spot car parks
when car leaves
write made to update ticket/car liscence plate to time left
when payment made write made to payment table to store transaction record
transaction api is triggered to credit card api
basic relational db can be used, will need to have classes
Explain any trade offs you have made and why you made certain tech choices...
sensors can fail and not have accurate tally of available spots
if payment system down car's won't be able to leave and revenue may be impacted
know what im doing