architecture

November 13, 2014

Distributed Databases and Replication Design

One of the most important elements of distributed database architecture is replication. In fact, it defines the database architecture. It determines whether or not the data is consistent / available.

Master / Slave

Writes are executed on master nodes, replicated to slave nodes. If consistency is required, reads are executed on master nodes. If it is not, reads are executed on master nodes and / or slave nodes.

 

Read more »

April 29, 2014

When Big Data is Slow

The key to being successful in big data initiatives is being able to manage the speed, scale and structure at sub-millisecond speed.

Big Data is a big term. It encompasses concepts about data types, dozens of different technologies to manage those data types and the eco-system around all those technologies. And everything in it moves fast!

Read more »

March 5, 2014

Topology: The Architecture of Distributed Systems

You can’t judge a book by its cover, but you can judge the architecture of a distributed system by its topology.

If two distributed systems are equally effective, is the one with the simpler topology the one with the better architecture? This article compares the architecture of two document databases and two wide column stores by looking at their topologies.

Read more »

January 20, 2014

Introducing the Couchbase .NET SDK 2.0 Development Blog Series

Hello folks, over the next couple of months we’ll be doing a series of blogs that will follow the development of the Couchbase .NET 2.0 SDK. In this post I will go over the high level architecture, some motivation and features you should expect, and what the overall goals are of the .NET SDK with respect to the other Couchbase clients: Node, PHP, Java, and C.

Read more »

March 22, 2013

Performance Oriented Architecture

"How should I access my data?" is often asked by developers as they contemplate a storage solution. To answer that question one first needs to understand the application under consideration. Who are the most important users, and which use cases need to be fast—that is, what actions does the user take a lot? What is the hot path?

Read more »