High Availability | Eliminate Single Points of Failure | System Design Concepts for Beginners
Vložit
- čas přidán 1. 07. 2024
- System Design Concepts for Beginners. This playlist should help you prepare for your system design interviews.
This video covers the topic of availability. What is availability in system design, how is it measured and how to design highly available systems.
Systems design interview prep guide -
• How to Prepare for Sys... - Věda a technologie
Adding more information about floating IP :
The floating IP design pattern is a well-known mechanism to achieve automatic failover between an active and standby pair of "stateful hardware nodes" (media servers).
A static secondary virtual IP address is assigned to the active node. Continuous monitoring between the active and standby nodes detects failure.
If the active node fails, the monitoring script assigns the virtual IP to the ready standby node and the standby node takes over the primary active function. In this way, the virtual IP floats between the active and standby node.
I watched a couple videos on this stuff and yours is the one where I learned the most out fo all of them!
Thank you, thank you!!
You should implement a real life example of this session.
Please do more videos on more subjects, when in doubt, when thinking that a subject is well covered online - go for it, make tutorials about it. You've got an ability to teach!
Thanks! Working on more system design videos for this playlist :)
I have a problem. WHY DID YOU STOP UPLOADING. Your content is gold.
Thank you so much Shiran for your Charitable Contributions. Loving your videos. Salute!!!
This is information wrapped in gold. Thank you so much🌟💙
your content is gold, this deserves more views
Very high quality video. Great audio, video, etc, and the concepts are explained so well. Definitely helped me.
Awesome! Glad to hear :)
Great video.Absolutely great video.
This was an excellent video explaining high level and some technical aspects of HA!!
Thank you! You have a great content and you explain it straight-forward for beginners to understand the concept of system design. Looking forward to your videos!
Great video with a very clear explanation
wow, looking forward to this, your videos are really professional and well made
thanks
excellent job
Your videos are best system designed and awesome. The way you connect dots are cool and easy to remember.. Atleast Today I understood. Why we need all the components
Please make more videos. As soon as possible I have interview of system design. Or if u can suggest any book.
Take care Have nice day
That’s awesome! Really glad it helps :)
It's absolutely perfect explanation , people will understand clearly
Thanks 😊
Hey Shiran i didn't know that this was ur first System design video on this channel .I thought this one was like just some another video of urs on the same concept which is the reason why i watched it 3 days late .(May be cause i subscribed u recently ) i was wondering if you could continue with SD videos moving from basics to advanced in the coming time . Me being passionate towards Cloud computing , have an idea that i may come across some Docker and Kubernetes videos on this channel . Too much to ask but anyways m looking forward to some System design content . All the best ur efforts are being appreciated by people😇👌👍
I’ve been binging your system design videos. These are hands down the best videos covering the various topics. Thank you 🙏🏼
Thanks you! Glad you enjoy them 🙂
@@ShiranAfergan could you share system design videos on apps like OTT. as it deals with large vol of data
You are awesome. So nice videos. :)
Thanks a lot for the informative video Shiran. I have few queries.
1. Does Floating IPs reside inside an API Gateway? if not, where does it fit in the entire architecture?
2. In DNS based load balancing approach, there are some DNS servers that allow instant removal of a dead load balancer domain, such as Amazon Route 53 or other third party DNS providers that have a built-in health check feature so that we do not need to wait until TTL expiration? Am I correct?
3. What is the order in which a load balancer and an API gateway are implemented in the system design of an application? which comes first?
Seriously Awesome explanation Ma'am 😊.
Try doing only System design videos more frequently 🙏
Thanks! there are more of these in the works :)
@@ShiranAfergan Please do let know, if there is a paid course from your end! waiting for more content! Amazing :D
9 : 28 ✌I liked that she took the name of my Country in her example ! ✌
🔥🔥🔥kindly make full course on Lld and hld mam ,there is no where i find curated course
When the residents of a country can answer questions conceptually (as opposed to personally), there is
= no single-point-of-failure
= and
= the baseline for the weakest-link in a chain is raised.
Same as system-design
I am wondering about your opinion on "client-site" availability approach (w/o load balancer) where a client keeps the list of service endpoints/aliases and decides where to send a request based on connectivity status and possibly some basic telemetry data from the service?
Pros:
* Cheap (no extra infra, simple code)
Cons:
* Added complexity on client
* Client needs to contain a list of domain-names / services, which makes migrating difficult (think of a mobile client that ships with a set-code). -> This is addressable by the server sending an updated config periodically
* Server implementation details leak onto client, which can sometimes be a security risk (what if someone gets an endpoint and just pings that endpoint exclusively?)
* Harder to update implementation - once the client ships, it's hard to enforce everyone to be up-to-date if there's a critical fix.
Imo, this is a good thing to discuss, it does have some pros and cons, but really depends on your use-case. IMO, the security risk is a big thing to consider.
Show the content, you're describing more.
To keep people concentrated ,please
lol then the dns monitor also is a single point of failure