The first part of this series gives an overview of the considerations that should be taken into account when sizing a Couchbase Server 2.0 cluster for production. The second part takes a deeper look at specific use cases and scenarios.
You're probably aware of the new Cross Data Center Replication (XDCR) feature of Couchbase Server 2.0. Its most obvious utility is to allow you to replicate data from one Couchbase cluster to another. However, there are more novel use cases for XDCR. One of the more notable examples is Couchbase and Elastic Search integration.
Early this morning, Couchbase 2.0 was officially released. The release is a big step forward for the Couchbase open source project and, in my opinion, has the potential to shake up the NoSQL landscape. You can read all about the new features and capabilities in other blog posts but I’d like to focus here on why I think this release is significant.
Let me start-off with the big news first. Couchbase Server 2.0 is here! I am thrilled to announce the availability of this major release. Couchbase Server 2.0 transforms Couchbase into a document database allowing users to build richer and more powerful web and mobile applications. You can now use Couchbase either as a key-value store or a document database based on your application requirements.
It is an exciting time to be at Couchbase. And, I get to kick off my first blog post with the announcement of the 2.0 release of our document database. It is my privilege to be a part of a team that is bridging the world of distributed/clustered systems with managing large unstructured and semi-structured datasets.
Setting up Couchbase Server can be really easy but if you haven’t installed it yet, here are step-by-step instructions. If you’re new to Couchbase Server 2.0 and are wondering what’s new, this blog will give you a quick tour of the product and explain a few key concepts. So let’s get started.