Words from the special myNoSQL sponsor, Couchbase:
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.
Wow. There is a lot going on here. There are four node types and two layers of logical groupings.
Nice. Simple. There is one node type.
Which document database would you choose?
- Which one is going to be easier to deploy?
- Which one is going to be easier to maintain?
- Which one is going to be easier to scale?
- Which one is going to be more resilient?
I believe the less moving parts, the better.
Original title and link: Topology: The Architecture of Distributed Systems [sponsor] ( ©myNoSQL)
Snapdeal selects Aerospike to improve shopper satisfaction over MongoDB, Couchbase and Redis [sponsor]
Words from the long time myNoSQL supporter, Aerospike, reporting on a success story of a customer deploying Aerospike to deal with massive demand growth:
After experiencing 500% growth in 2013, Snapdeal, India’s largest online marketplace, switched from 10 MongoDB servers to just two Linux servers on Amazon EC2 with Aerospike, and reduced response times to less than a millisecond.
Read the case study to learn more.
Original title and link: Snapdeal selects Aerospike to improve shopper satisfaction over MongoDB, Couchbase and Redis [sponsor] ( ©myNoSQL)
A 4-part series by Mike Bostock describing various integrations paths of D3 and CouchDB:
- Part 1: saving a D3 app in CouchDB
- Part 2: storing D3 library in CouchDB and storing data in CouchDB
- Part 3: accessing CouchDB data from D3
- Part 4: data import
Original title and link: Integrating D3 with CouchDB ( ©myNoSQL)
In the words of the special sponsor, Couchbase:
Kelly knew it. The U.S. Navy knows it. You know it.
Keep it Simple, Stupid (KISS)
We categorized NoSQL implementations. The categories include distributed caches, key / value stores, and document databases. However, what if application requirements span multiple categories? Do you add Redis, Riak, and MongoDB? The result would not be simple, stupid.
Let distributed caching, key / value storage, and document handling be use cases. The solution is a single NoSQL implementation that supports multiple use cases. In fact, Viber recently solved this problem. Their previous architecture relied on MongoDB for document processing and Redis for distributed caching. Their current architecture relies on Couchbase Server as a single replacement for both MongoDB and Redis. Read the full story.
Original title and link: The NoSQL KISS [sponsor] ( ©myNoSQL)
From IBM to… IBM: The short, but complicated history of CouchDB, Cloudant, and a lot of other companies and projects
Damien Katz created CouchDB after working at IBM on Lotus Notes: CouchDB and Me. CouchDB went the Apache way. Then things got complicated…
On the West coast, Damien Katz and a team of committers created Couchio, later renamed to CouchOne, later merged with Membase to become Couchbase, which finally dropped CouchDB. Damien Katz left Couchbase.
East Coast, Cloudant took CouchDB and made it BigCouch. I thought that Cloudant will be the CouchDB company — and in a way it was. Cloudant put BigCouch on the cloud as a service and on GitHub as open source. BigCouch is supposed to get back into Apache CouchDB, but many months later this hasn’t materialized yet.
To complete the circle, today IBM announced signing an agreement to acquire Cloudant — news coverage on GigaOm, BostInno, TechCrunch. Which probably makes sense considering Cloudant’s relationship with SoftLayer and IBM’s $1 billion Platform-as-a-Service Investment, but less so if you consider the IBM and
Anyways, the future of Apache CouchDB is bright. Yep.
Original title and link: From IBM to… IBM: The short, but complicated history of CouchDB, Cloudant, and a lot of other companies and projects ( ©myNoSQL)