well this was quite clearly explained , really thanks for this

spotify thick client hota hai ya thin?

Mam are notes available??

Great series mamm🔥, catching up to system design very fast

How can order and inventory services work in an asynchronous fashion? Order service needs to know the inventory availability to create a successful order and send the client with success/failure response and this can only happen synchronously. Am I missing something?

One by one quality videos with such a great yet simple explanation! Thanks!! :)

I have a question, is this same as the service layer in the MVC architecture? Like your controller -> Service class -> repository where controller does not do the transfermations or apply business rules or calls the database instead the service calls does this process. Can we call the service class as facade class here?

Another expectional video, thanks!! :)

This was something extraodinary! Explanation was crystel clear. Thanks a ton for this! :)

You have not added resources in the description. I only see paid courses websites

Could you please update your slide? PUT: To update an entire resource in one go and PATCH: To partially update a resource.

Hi my name is yogith 🫠

4:05 as a gujarati Jiga bytes is very funny it's gujarati nick name of jignesh 😅😅😅😅

Finely, something understandable!

Very good explanation!!

Thanks for thats explication.

thnaks

I waste of my time to see this video. Take 9 min and explanation uffff.

Madam why are you talking so anxiously....explain the concept patiently bit slower pace....explanation is good but going faster at the end.

❤

Crisp and clear explanation who is completely new to HLD & LLD. Thank you so much for the starter video & giving brief about these two hot shot topics in SD round.

Love these videos. Please continue making more such wonderful videos. Looking forward to the Video on CQRS

Thank you.

Beautiful

thanks a lot ma'am, u have explained very nicely!

Awesome tutorial for explaning Asynchronous call but It would have been better if you create one Asynchronous REST API through coding.

nice

Thanks so much for explaining Scaling with a perfect example!

Really like the way you explain concepts!

Quiz Answers: List down the real-world use cases when you would choose a thick client architecture over a thin client architecture and vice versa. Thick client architecture could be used in scenarios where sending all the details to the server is not really valuable. Ex: Image/Video editing software, Word processor, Pomodoro Timer App Pros: 1. Low/No dependency on network 2. Good performance 3. Rich UI Cons: 1. Client binary size may be bigger 2. Releasing new changes may not be easy Thin client architecture could be used for apps that are mainly used for presenting information in a nice way and need not do any intensive logical computation at the client app. Ex: Photo Viewing App for Photo Stored on the Drive, Web-Based Email Client Pros: 1. Lightweight client binaries 2. Low-cost devices too can run these easily 3. Centralized management can enable synchronization across devices Cons: 1. Heavy dependency on network 2. Performance may be impacted due to network speed 3. Any change in the functionality of the new release has to be done Can you think of a system that has thick clients, thin clients, and multiple tiers? Applications like Word, Excel, and PowerPoint 1. Thick Client: Desktop versions 2. Thin Client: Web Based clients of these apps Multiple Tiers - Instagram, Netflix, etc Also, can servers behave as clients? Yes, servers can behave like clients to other servers and can communicate using REST/RPC, etc protocols.For example, app servers act as clients to a DB server.

I don't think the code is following open closed principle, the code should be open to extension but closed to modification, if we needed to add a new university, more branched if-else statements will have to be written, which is a clear violation of the open closed principle, great video nonetheless!

What if there is a class which requires methods from both the interfaces?

Wow. A simplest way to explain an unknown. Your presentation skills are good. Talking slowly, clearly with simple words are plus. Examples chosen are also good. great job.

This is an excellent resource, thank you!

I have a question, In case of UPSERT, if the resource doesn't exist and the new resource is created along with the ID that has been passed, Then what should be the response code? 201 or 200?

Hashing comes from the dish name Hash brown , wow😂😂😂😂

Wr are you mam please make more videos

Best explanation 👍

Please give detailed video on rate limiting & headers

It is not explained correctly in the video as if the number of parameters changes, the interface can't help. And if cache technology changes, an interface is not needed. So, in both the cases we can proceed without an interface.

Thank you :)

Hi Yogita, you are a blessing for all the engineering students and working professionals in climbing up the ladder to their dream job. Thanks a lot for taking the initiative to share the learnings of your experience with the student community. I wish educators like you grow more and more!!!

Thank you :)

Thank you :)

I really likes the way you teach! Detailed, On the Point. Thank you so much maam for this kind of content🔥.

Awesome editing!!

Many basic mistakes in this video (that are easy checkable). 1) 409 error can be also thrown from PUT request From MDN: "Conflicts are most likely to occur in response to a PUT request. For example, you may get a 409 response when uploading a file that is older than the existing one on the server, resulting in a version control conflict.") 2) PUT 'must' be idempotent and PATCH is not necessary idempotent. For example you can have an array of items on server and every time PATCH request will be made item will be added to an array. But with PUT you should send the whole array which will be replaced (so every other same request will not change any resources just replace it with same resource). Of course PATCH can also be idempotent is some situations (but it is not necessary). From MDN: "A PATCH is not necessarily idempotent, although it can be. Contrast this with PUT; which is always idempotent. The word "idempotent" means that any number of repeated, identical requests will leave the resource in the same state.")

Ma'am can you make video on hands on Event driven approach implementation.

Like your content and presentation. Yes, please do make video on Monitoring. it's a confusing topic in context of microservices.

In the degree (CP) and node B is writing and eventually read happens in node a it will return the wrong data right, how it is consistent than