Відео

Very bad overall video.

enum is not grenerally suggested

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.

is this Architecture design ?

This was beautifully explained! Please continue making such great videos. This was really helpful.

You don't need an entire new service just for pricing policy.

Why do we need three databases can't we make more tables

size per sot 1K, 1K what? bits, bytes, be clear na

Why no videos ..your videos are good

Simple and elegant solution to start with. This is very helpful for beginners. Can you also create a video on Elevator design problem?

Excellent work.

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.

Hi, Please upload more videos. Your videos are more crisp, clear and brief.

Nice ,very short and to the point.

best PL system design video

I think for communicating between cart manager end list manager events should be used instead of normal methods

brilliant

please pronounce it as deta & not data it's detabase & not database

Great content

great video! are each of those yellow blocks its own repo hosted on its own machine?

it is a great video. Thanks. when you talk about "user manager", "list manager" ... are they the microservice?

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.

Great Great Video. SImple and Clear

Brilliant!

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.

slot allocation may not be required. This should be discussed with the interviewer as you may want the vehicle to be parked in any available slot.

Super bulshit solution. Parking lot is a low level design question and not distributed system solution 🤦

nice info

ua-cam.com/video/sdL1fmzFj_w/v-deo.html

Very good video. Expecting more videos from you, Sir 👍🏻

Great explanation. Really helped a lot to understand low level and high level designs. Please add more videos on low level designs.

You are simply amazing!

Basics explained well

very well explained

Very nice and informative video ! Thanks for sharing this.

Bonus tip: Listen to it in 2x

Thankyou so muchhhhhhh.

Awesome explanation.

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 ? ....

good approach

nice been trying to create an ecommerce website

I like how you provided a 'Further Reading' section. Helpful to know what other important concepts to know.

You seem like a knowledgeable guy

Nice

Thanks for the video!!

In 3:35, where are the number of vehicles entering per day?

Excellent.

Clear Explanation!

Very clearly explained, thank you! Looking forward to seeing more of your videos

great video