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



hardware: All content tagged as hardware in NoSQL databases and polyglot persistence

Storage Pod - 180TB and Probably Growing

We thought ten people would care; instead a million people read our Storage Pod 1.0 blog post where we open sourced the Backblaze Storage Pod design and introduced the world’s most cost-efficient way to store big data. […] Today we introduce Backblaze Storage Pod 3.0 which stores more data, costs less, is more reliable, and is easier to service.

Because my knowledge of building hardware stuff has been stable around zero for-ever, I enjoy quite a bit at least reading about it.

the HN thread

Original title and link: Storage Pod - 180TB and Probably Growing (NoSQL database©myNoSQL)


Big Data Done Cheap

Quentin Hardy for NYTimes about Violin Memory data cards.

The Violin Memory data cards, produced in conjunction with Toshiba, offer 1.4 terabytes in “flash” memory, which can be accessed quickly. Cards for higher-end servers hold up to 11 terabytes.

Everything’s sounds great, right?

The low-end Violin Memory card has a list price of $4,000, and is intended for use in a server costing even less than that. A bigger card, for the kind of server that costs $5,000 or more, lists for about $60,000.

Cheap can mean so many things.

Original title and link: Big Data Done Cheap (NoSQL database©myNoSQL)


Facebook Open Compute: A New Database Server Design

Facebook has released under the Open Compute umbrella the design of a new database server they’ve introduced in one of the datacenters. The bit that caught my eyes is that this is not about more disk space or more CPU, but redundant power supplies:

According to Frankovsky, for certain database functions at Facebook, it was more important to have redundant power supplies for a database node than it was to have multiple compute nodes in an Open Compute V2 chassis sharing a single power supply. […] Frankovsky said that by doubling up the power supplies and making an Open Compute-style database server, it was able to cut the costs over its current database servers by 40 per cent.

The spec can be found ‎here (PDF).

Original title and link: Facebook Open Compute: A New Database Server Design (NoSQL database©myNoSQL)