Oren Eini discusses the building blocks of a reliable, transactional distributed database, covering ACID compliance, consistency, failure handling, monitoring, management, and more.
Dan North describes a model for thinking about the age of code and argues for replaceability as a first class concern, ending up with something that looks a lot like microservices.
Peter Bourgon provides a practical introduction to Conflict-free Replicated Data Types (CRDTs) and describes a production CRDT system built at SoundCloud to serve several product features.
Aviran Mordo introduces Wix's architecture, a highly available eventually consistent system, along with patterns for rendering many websites with a relatively small number of servers.
Michael Nygard discusses several loopholes in the CAP theorem that can be used to engineer practical, real-world systems with desirable features.
Garrett Eardley explores how Riot Games is using Riak for their stats system, discussing why they chose Riak, the data model and indexes, and strategies for working with eventually consistent data.
Sean Cribbs compares ACID with BASE, explaining the virtues and tradeoffs of eventually consistent systems and what developers should know in order to feel comfortable working with EC systems.
Eric Evans discusses three DDD patterns helping embedding CAP tradeoffs inside the domain model: Aggregates, Domain Events and Bounded Contexts.
Sean Cribbs discusses Convergent Replicated Data Types, data structures that tolerate eventual consistency.
Reid Draper introduces Knockbox, an eventual consistency toolbox for Clojure inspired by Statebox, discussing some useful use cases, how to perform garbage collection and testing while using it.
Bob Ippolito explains how to solve concurrent update conflicts with Statebox, an open source library for automatic conflict resolution, running on top of Riak.