Highly Consistent Database

  • -1

    _aman 10 months ago

    fault tolerant
    distrinuted

    reply
  • -2

    shyam_ 10 months ago

    what if one of the node in a shard goes down and comes online after sometime. Will the master invalidates the entries belong to the that particular node?

    reply
  • 3

    raviteja_yakkaladevi 10 months ago

    What are the cons if we use last modified time(solution given in highly available database with W+R>P) for knowing where the block is instead of maintaining a master?

    reply
    • 0

      KMeshU 7 months ago

      What if the last modified node itself goes down

      reply
      • 1

        raviteja_yakkaladevi 7 months ago

        W+R>P. This ensures the consistency even in the case that you were saying. You can read it here https://www.interviewbit.com/problems/highly-available-database/

        reply
    • 0

      piscado about 1 month ago

      i think this "master" (or i'd say logger) simply acts like a write lock. for the previous high-A architecture, a read can be done in the process of a writing and gives stale data. in this case, on the other hand, we always know if the writing is finished since every read is going through the "master"

      reply
  • 2

    sarang 10 months ago

    how at paxos or raft?

    reply
  • 0

    steven_chow 4 months ago

    What are the advantages for this solution comparing with the high availability solution with Casandra when R == W == Replication Factor?

    reply
    • 2

      resurrectedVaibhav 4 months ago

      Cassandra/Dynamo solution is actually a complex solution and is focussed on business scenarios where writes are very frequent.
      That solution is not consistent in case of failures if you notice. I think the only way to make it consistent is to have a higher value of W + R thus decreasing the performance. Also, not to forget that to resolve vector-clock conflicts we need a complex algo in the client.


      Though here the load is not truly distributed.

      reply
  • 0

    shiyi_chen 4 months ago

    distributed transaction

    reply
  • 2

    samira_allahverdiyeva 3 months ago

    first, you said QPS is "Let's assume around 100k"m in the Assumptions part you say "Total estimated QPS : Around 10M ". I didn't get this part

    reply
    • 0

      sunnyk 2 months ago

      I agree, there is inconsistency in this requirement I think. would be safe to assume one and go ahead with that.

      reply
Click here to jump start your coding interview preparation