Need advice about which tool to choose?Ask the StackShare community!
CouchDB vs Google Cloud Storage: What are the differences?
Developers describe CouchDB as "HTTP + JSON document database with Map Reduce views and peer-based replication". Apache CouchDB is a database that uses JSON for documents, JavaScript for MapReduce indexes, and regular HTTP for its API. CouchDB is a database that completely embraces the web. Store your data with JSON documents. Access your documents and query your indexes with your web browser, via HTTP. Index, combine, and transform your documents with JavaScript. On the other hand, Google Cloud Storage is detailed as "Durable and highly available object storage service". Google Cloud Storage allows world-wide storing and retrieval of any amount of data and at any time. It provides a simple programming interface which enables developers to take advantage of Google's own reliable and fast networking infrastructure to perform data operations in a secure and cost effective manner. If expansion needs arise, developers can benefit from the scalability provided by Google's infrastructure.
CouchDB belongs to "Databases" category of the tech stack, while Google Cloud Storage can be primarily classified under "Cloud Storage".
"JSON" is the primary reason why developers consider CouchDB over the competitors, whereas "Scalable" was stated as the key factor in picking Google Cloud Storage.
CouchDB is an open source tool with 4.22K GitHub stars and 833 GitHub forks. Here's a link to CouchDB's open source repository on GitHub.
Evernote, Bugsnag, and Wix are some of the popular companies that use Google Cloud Storage, whereas CouchDB is used by Acadar, Third Iron, and SocialDecode. Google Cloud Storage has a broader approval, being mentioned in 179 company stacks & 74 developers stacks; compared to CouchDB, which is listed in 60 company stacks and 30 developer stacks.
We choose Backblaze B2 because it makes more sense for storing static assets.
We admire Backblaze's customer service & transparency, plus, we trust them to maintain fair business practices - including not raising prices in the future.
Lower storage costs means we can keep more data for longer, and lower bandwidth means cache misses don't cost a ton.
We implemented our first large scale EPR application from naologic.com using CouchDB .
Very fast, replication works great, doesn't consume much RAM, queries are blazing fast but we found a problem: the queries were very hard to write, it took a long time to figure out the API, we had to go and write our own @nodejs library to make it work properly.
It lost most of its support. Since then, we migrated to Couchbase and the learning curve was steep but all worth it. Memcached indexing out of the box, full text search works great.
We offer our customer HIPAA compliant storage. After analyzing the market, we decided to go with Google Storage. The Nodejs API is ok, still not ES6 and can be very confusing to use. For each new customer, we created a different bucket so they can have individual data and not have to worry about data loss. After 1000+ customers we started seeing many problems with the creation of new buckets, with saving or retrieving a new file. Many false positive: the Promise returned ok, but in reality, it failed.
That's why we switched to S3 that just works.
Pros of CouchDB
- JSON43
- Open source30
- Highly available18
- Partition tolerant12
- Eventual consistency11
- Sync7
- REST API5
- Attachments mechanism to docs4
- Multi master replication4
- Changes feed3
- REST interface1
- js- and erlang-views1
Pros of Google Cloud Storage
- Scalable28
- Cheap19
- Reliable14
- Easy9
- Chealp3
- More praticlal and easy1