Availability | System Design Interview Basics 2022

[@ozobi2961]

Great teaching. I wish you had more views and support cause these are excellent.

[@big_tech_coach]

Thank you Oz, I will get there no worries!

[@voidpointer398]

This was easily one of the best videos on availability patterns. Thank You

[@big_tech_coach]

Thank you Jatin, that's very kind of you! 😋

[@mopsyched]

Good work Lad! To summarize: Availability is removing a single point of failure or ensuring your average downtime over a UNIT (year, month, xzy) is as low as possible. Many companies have SLAs 99.9%.. which means Availability is not 100% uptime (this is more tightly coupled to reliability). Availability is a High-level topic or best practice since its a BIG PICTURE. Best practices include: 1. redundancy( Nodes/Process) : DB level App Level Ensures backup nodes to take controlled of lost node Example: Multiple Redundant DCs, or More Primary and secondary nodes (Active Passive ). 2. Replication of Data : or Making those out of sync redundant nodes synched or ensures consistency (eventual or perfect) 3. Fail Over strategies set ( SINGLE LEADER, MULTIPLE LEADERS). 4. Load Balancers

[@big_tech_coach]

Thank you Mujtaba!