Operation-based CRDTs: registers and sets

Last time [https://www.bartoszsypytkowski.com/operation-based-crdts-protocol/] we started our operation-based CRDTs sub-series, as we moved away from state-based CRDTs. We talked mostly about core requirements and sample implementation of RCB (Reliable Causal Broadcast) protocol, which was necessary to provide…

Operation based CRDTs: protocol

Today we'll continue a series about CRDTs, this time however we'll stray from the path of state-based CRDTs and start talking about their operation-based relatives. The major difference that we need to cover, is the center…

Make your cluster SWIM

In this blog post we'll cover how systems form clusters, what clusters actually are and what are their responsibilities. We'll also present different protocols responsible to serve the needs of the clusters with a various tradeoffs…

State-based CRDTs: Maps

In this blog post, we'll cover the idea of CRDT maps, and how we could create them and utilize them in common scenarios. A prerequisite for this talk is some general knowledge of CRDTs, especially observed-remove sets [https:…

Building custom fibers library in F#

Over the course of last few months on this blog post, I've been sharing about internals and how-to of different concurrency patters. We discussed how to implement our own actors [https://www.bartoszsypytkowski.com/build-your-own-actor-model/] and specific affinity-based…

Thread safety with affine thread pools

In the previous blog post [https://www.bartoszsypytkowski.com/build-your-own-actor-model/] I've written about building a thread-safe state access by using actor programming model (as opposed to common practices requiring synchronization barriers with locks) without compromising performance coming with…