When distributing data leads to lots of small messages around a cluster then network latency and the request processing time (including serialization, deserialization of the request on the server side) can add significant overhead.
A Fixed Partition provides a good way to distribute data over many nodes when clients are accessing a single key at a time. If, however, a client wants a
When partitioning data across a set of cluster nodes we need a uniform distribution and to be able add and remove nodes to the cluster without causing a lot of data to be moved around. Unmesh Joshi explains how to
Peer-to-peer systems treat each cluster node as equal; there is no strict leader. This means there is no explicit leader election process as happens in the Leader and Followers pattern. However, there still needs to be one cluster node ac
Although he's been quiet for a while on here, Unmesh Joshi has been working hard on more of his Patterns of Distributed Systems. In this first of a new batch, he looks at the difficulty of getting consistent rea
When I'm writing, or mentoring others in writing, about a particular technique I prefer to take the role of an educator rather than that of an advocate. When doing that, I see two main stances an author can take. One is to focus on the trade-offs between this technique and its alternatives, the other is to focus on the merits of the particular technique and not discuss the alternatives.
Legacy systems often act as integration hubs, ingesting source data to pass on to downstream systems. A new downstream system can decouple itself from legacy by finding the source of data to the legacy and integrating directly to that instead.
Legacy systems often act as integration hubs, ingesting source data to pass on to downstream systems. A new downstream system can decouple itself from legacy by finding the source of data to the legacy and integrating directly to that instead.
Many software teams describe desired product capabilities as a product backlog: a list of user stories. These stories capture who needs the work, what the work is, and why it's needed. Too often teams expect a product owner to be the sole source of the b