Over a million developers have joined DZone.

Cloudant Secures your Data with BigCouch 0.4

DZone's Guide to

Cloudant Secures your Data with BigCouch 0.4

· Cloud Zone ·
Free Resource

Learn how to migrate and modernize stateless applications and run them in a Kubernetes cluster.

A legitimate worry for anyone on the cloud is the fear of damage to the physical servers where your data is stored.  Cloudant is a company that offers an integrated database, search and analytics in order to provide businesses with a platform based on Apache CouchDB.  Their platform is currently open source, and is also available in hosted and managed deployments.  

Today, Cloudant released BigCouch 0.4, which adds new 'zone' functionality to help users control where they put data copies.  This is good news for those of you worried about the potential unexpected loss of data on the server side.  Now, using zones on BigCouch can allow the same data set to be stored in different locations.  The Cloudant Blog offers one example of the potential of using zones . . .

. . . our west coast cluster “Meritage” is actually spread over two different data centers in two distinct geographic regions. We use zone-support to ensure that at least one copy of all of our customers’ data exists in both locations. That way, if one location falls into the ocean or is subject to nuclear attack, our customers’ data is still safe and available. With this feature now in BigCouch, you can extend clusters across multiple locations.

BigCouch 0.4 also adds support for the replicator database to help manage multiple replications, according to the release post.  If you're interested in trying out BigCouch 0.4, you can find basic usage instructions here.  You can also find the entire list of performance improvements in the BigCouch 0.4 here.  If you've spent some time on the latest BigCouch, give us some of your comments.

Join us in exploring application and infrastructure changes required for running scalable, observable, and portable apps on Kubernetes.


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}