It's most likely just handles metadata, aggregated data or serves as a proxy to their main DB. I just can't believe they converted 10 PB of binary data into JSON ;)
Why Large Hadron Collider Scientists are Using CouchDB
11–17 of 17 posts
Re: Why Large Hadron Collider Scientists are Using CouchDB
#12It's most likely just handles metadata, aggregated data or serves as a proxy to their main DB. I just can't believe they converted 10 PB of binary data into JSON ;)
Re: Why Large Hadron Collider Scientists are Using CouchDB
#13It's most likely just handles metadata, aggregated data or serves as a proxy to their main DB. I just can't believe they converted 10 PB of binary data into JSON ;)
Re: Why Large Hadron Collider Scientists are Using CouchDB
#14I have no idea why they don't use something dynamo based like Riak or Cassandra which actually can automatically shard data and scale really well... CouchDB only supports replication, no sharding unless you use third party libraries. With Riak they could use the internal map/reduce support and with Cassandra they might be able to use Hadoop to analyze data and split the workload over several nodes.
They use it to store aggregated reports for distribution and analysis. It isn't doing any heavy lifting, and it's not a terribly compelling case study of anything.
Re: Why Large Hadron Collider Scientists are Using CouchDB
#15I have no idea why they don't use something dynamo based like Riak or Cassandra which actually can automatically shard data and scale really well... CouchDB only supports replication, no sharding unless you use third party libraries. With Riak they could use the internal map/reduce support and with Cassandra they might be able to use Hadoop to analyze data and split the workload over several nodes.
If you read the case study you will see that building apps rapidly was a huge win for them. CouchDB gets compared with other DB's but it is a full stack app dev environment. The other NoSQL DB's need a Rails or PHP or Python or Java or C# or ... stack in front and app dev is nowhere as fast as with CouchApp.
Re: Why Large Hadron Collider Scientists are Using CouchDB
#16It's most likely just handles metadata, aggregated data or serves as a proxy to their main DB. I just can't believe they converted 10 PB of binary data into JSON ;)
Re: Why Large Hadron Collider Scientists are Using CouchDB
#17I am happy to see that CERN uses Oracle extensively, presumably for the data that matters. Our tax dollars should only go to a reliable, proven database solution.