This is a basic explanation of the service, which is good as a starting point. However, there are many other questions that an interviewer might ask. For example: 1. why do you need to store 10 years of parking lot information ? 2. Why do you need 3 DBs if you have only 4GB of data ? 3. How do you plan to implement the lock ? 4. What happens if a node goes down ? ....
What I liked about your video was you discussed about concurrency. I looked this question at multiple places but none actually tried to explain this. Thanks for this.
Hey, I have been looking at a lot of system design questions but none of them were as simple as this and rest of your videos. It's perfect for a new grad with no prior experience. There are no unnecessary details which make it more confusing. Thanks a lot
Nice & clean explanation. Fills up with good ideas from both a System Design as well as an OO Design perspective. Leaves enough room for imagination. :)
Very helpful video. Covered all the topics nicely (w/o rushing into implementation :-) ). I can suggest few more topics System design for 1. message chatting service which is highly scalable, distributed, resilient, supports encryption of message end to end (i.e. server cannot see message) 2. Photo sharing service like instagram 3. Cab booking service like uber (Given APIs for GPS/ map) 4. Book recommendation service (Video recommendation service) 5. Service to show trending topics etc
Thanks for using easy-to-understand and simple language. Just a suggestion if you can add a link of the PPT/PDF that you have used while creating videos. It will help to revise concepts easly.
Thanks, Nice Explanation. It leaves a lot of open questions related to failure scenarios handling. like what happens if slot service books the slot but ticket couldn't be generated. How do you say to slot service to roll back the booking? what if you couldn't communicate to the slot service to unbook the slot. Will you have a background job for checking slots that are booked but no one was given a ticket against, due to technical failure. Similar scenarios can happen with exit case, slot unbooked, and later booked by other person but ticketing service fails to let the first-person exit. now if you retry, to unbook the slot you may end up unbooking the slot that was reserved by another person.
if the slot has booked and ticket is not generated. we can do retry insted of rollback. because the major thing here is the getting parking lot rather than the ticket. Ticket can be regerated for same parking lot but we can not assign two parking slot to one vehicle.
I have a comment here, Everything looks ok to me. Except why do we need to track the status of parking. Even though status of parking we can find from ticket#. Whether parking is available or not. In this case we would need to make an unnecessary call to the table. Which is not at all required.
Calling the use case “giving the user a ticket” is a bit off isn’t it? Nobody uses a parking garage to get a piece of paper, they use it to get a parking spot.
@@techinterviewguide4297 System design for 1. message chatting service which is highly scalable, distributed, resilient, supports encryption of message end to end (i.e. server cannot see message) 2. Photo sharing service like instagram 3. Cab booking service like uber (Given APIs for GPS/ map) 4. Book recommendation service (Video recommendation service) 5. Service to show trending topics etc
I like the explanation and I think it is a good job for questions like this. However, I wonder if you have ever seen an actual parking lot that assigned you a spot when you got your ticket? If you have, I can tell you that is very unusual.
Maybe you don't need the actual slot id in that case. We could just have a count of different types of slots(S, M, L) in DB/cache. And simply operate on the basis of that count. Concurrency becomes even more crucial then. And then instead of returning a slotId, we could return some other ID to the user. Could be Auto-incremented id, or we could propagate a Vehicle Id throughout our system, and just return that. Dunno if this works.
