Skip to content

Distributed Computing Musings

Deep dive into distributed computing concepts

  • Home
  • About Me

Month: January 2022

  • Home
  • 2022
  • January

Transactions: Read committed isolation

Ensuring that each resource is accessed and modified by a single user at a time is very complex on the application layer. This is why…

Posted on January 31, 2022January 31, 2022
  • Database
  • Transaction

Transactions: Atomicity & Isolation

In last post, we saw the use case of why we need transactions to maintain a consistent state of our storage system. A database is…

Posted on January 28, 2022January 28, 2022
  • Database
  • Transaction

Transactions: Why we need all or nothing?

In real life applications, things can go wrong for scenarios which you have never considered while designing the application. These failures can happen due to…

Posted on January 25, 2022January 25, 2022
  • Database
  • Transaction

Partitioning: Handling secondary indexes in partitions

Up until now we have discussed partitioning in a system where we are able to store a record in a partition and retrieve from the…

Posted on January 23, 2022January 23, 2022
  • Partitioning

Partitioning: Consistent Hashing

While ending our discussion on various approaches to partitioning, we saw how the typical hashing approaches fail when we encounter a node failure or when…

Posted on January 21, 2022January 21, 2022
  • Partitioning

Partitioning: Approaches to partitioning

Before diving into approaches to partition a database, let us clear up one thing in aspect of partition and its relationship with replication. Partitioning &…

Posted on January 19, 2022
  • Partitioning

Partitioning: Introduction to partitioning

Until now we have seen how replication helps in scaling a read-intensive workload. We keep one or more nodes as leaders that handle write traffic…

Posted on January 17, 2022January 17, 2022
  • Partitioning

Replication: Handling Concurrent Writes

In all the replication methodologies, we have seen a common issue which all of the replication methods fail to solve completely and that is handling…

Posted on January 15, 2022
  • Replication

Replication: Maintaining a Quorum

In Introduction to Leaderless Replication we saw that Quorum plays a huge part. We need some way to ensure that storage operations are persisted correctly…

Posted on January 11, 2022January 13, 2022
  • Replication

Replication: Introducing leaderless replication

Up until now in a single leader and multi-leader replication our assumption was that client will send an update request to leader which in turn…

Posted on January 10, 2022January 10, 2022
  • Replication

Posts navigation

Older

Recent Posts

  • Paper Notes: Firestore – The NoSQL Serverless Database for the Application Developer
  • Vector Clocks: So what time is it?
  • Lamport Logical Clock: One after the another. But not together.
  • How does your computer know what time it is and why will it break your distributed systems?
  • Paper Notes: Amazon Aurora – Design Considerations for High Throughput Cloud-Native Relational Databases

Recent Comments

  1. Vector Clocks: So what time is it? – Distributed Computing Musings on Lamport Logical Clock: One after the another. But not together.
  2. Event Sourcing: Removing UD from CRUD – WONDERFUL PORTAL on Event Sourcing: Removing UD from CRUD
  3. Paper Notes: Amazon DynamoDB – A Scalable, Predictably Performant, and Fully Managed NoSQL Database Service – WONDERFUL PORTAL on Paper Notes: Amazon DynamoDB – A Scalable, Predictably Performant, and Fully Managed NoSQL Database Service
  4. varunu28 on Paper Notes: Amazon DynamoDB – A Scalable, Predictably Performant, and Fully Managed NoSQL Database Service
  5. kapil jain on Paper Notes: Amazon DynamoDB – A Scalable, Predictably Performant, and Fully Managed NoSQL Database Service
Copyright © 2023 Distributed Computing Musings. All Rights Reserved