Availability | System Design Interview Basics 2022

Поділитися
Вставка
  • Опубліковано 9 лип 2024
  • Learn about Availability to ace your system design interview and get an offer of big tech companies like Facebook, Amazon, Apple, Netflix, Google. This video covers the availability patterns of Fallover and Repetition and what you really need to know about them to succeed at your system design interview.
    🔴 Subscribe for more on System Design Interview Preparation: bit.ly/3yohYks
    Learning System Design for Technical interviews can be hard. Big tech companies offer top of the market salaries, great working environment but also ask you to go the extra mile in interview preparation. This is your chance to build up the skills you need to get in!
    ⭐️ Contents ⭐️
    ⌨️ (00:00) Intro
    ⌨️ (0:23) Why does Availability Matter?
    ⌨️ (54:00) Business Impact of Unavailability
    ⌨️ (01:20) Availability in Numbers
    ⌨️ (02:16) The Struggle with Large Distributed Systems
    ⌨️ (03:08) Availability Patterns
    ⌨️ (03:23) Failover Pattern
    ⌨️ (03:44) Active-Passive
    ⌨️ (04:53) Active-Active
    ⌨️ (05:50) Replication Pattern
    ⌨️ (07:33) Primary-Replica
    ⌨️ (09:37) Primary-Primary
    ⌨️ (12:00) In the Interview
    🐦 Follow me on Twitter:
    / hinsencamp
    🙌 Our Big Tech Community on discord!
    / discord
    ✏️ Download FREE system component library for Excalidraw:
    bigtechcoach.gumroad.com/l/ex...
    ⭐️ Enrol to my 5.0-rated Course on System Design Interview Preparation:
    www.udemy.com/course/the-bigt...
    🚀 Ace your system design interview!
    #SystemDesign #InterviewPrep #Availability

КОМЕНТАРІ • 6

  • @mopsyched
    @mopsyched Рік тому +2

    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

  • @voidpointer398
    @voidpointer398 Рік тому +1

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

    • @big_tech_coach
      @big_tech_coach  Рік тому

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

  • @ozobi2961
    @ozobi2961 2 роки тому +1

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

    • @big_tech_coach
      @big_tech_coach  2 роки тому +1

      Thank you Oz, I will get there no worries!