ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

NoSQL Ecosystem News & Links 2010-03-19

  1. Royans K Tharakan: ☞ Pregel: Google’s other data-processing infrastructure. But we have graph databases and Gremlin. And it looks like Google will finally talk about it at ☞ Sigmod 2010.
  2. Brian Prince: ☞ NoSQL Database Movement Gains Ground as Alternative. Definitely I don’t agree with (just think about how many would benefit from “persistent memcached”):

    Matt Aslett, an analyst with The 451 Group, said that while distributed column stores like Cassandra have found a home in some situations, it’s the document-oriented databases like MongoDB, CouchDB and Riak that hold the most promise for enterprises in the short-term.

  3. William Webber: ☞ NoSQL: Awesome tech with a stupid name. Get over it!. If you don’t like it, don’t use it!
  4. Redis gets a new type: ☞ hashes. Interesting that Redis — a key-value store — is adding more smart data types that would make it even more appealing.
  5. Cyril Mougel: ☞ Oupsnow, an AGPL bug tracker in Rails using MongoDB and .
  6. Dare Obasanjo: ☞ Building Scalable Databases: Are Relational Databases Compatible with Large Scale Websites?:

    The problem with database sharding is that it isn’t really a supported out of the box configuration for your traditional relational database product especially the open source ones. How your system deals with new machines being added to the cluster or handles machine failure often requires special case code being written by application developers along with special hand holding by operations teams. Dealing with issues related to database replication (whether it is multi-master or single master) also often takes up unexpected amounts of manpower once sharding is involved.

  7. InfoQ: ☞ Facebook’s Petabyte Scale Data Warehouse using Hive and Hadoop. Remember putting your NoSQL data to work.