This is the story of how I learned to say ‘No’ to SQL and to cope with my wife’s addiction to Coach bags.

The answer is support groups. I kid. No, I don’t.

There are a number of alternatives to relational databases. However, for the purposes of this post, I am focusing on persistent, distributed key/value stores.

It all seems to have started with Amazon’s 更多相关的内容 »
讨论   把此链接加入于...  与朋友分享   已已沉
添加到:                  |   书签  

The days of the relational database being a one-stop-shop for all of your persistence needs are over. A new class of application is beginning to emerge with requirements that exceed the capabilities of the relational database. Some of these applications need unlimited scalability or bullet proof fault tolerance, while others may require blazing fast access or flexible data storage. The relational database was simply not designed to meet the needs of this small but growing class. Instead, a n 更多相关的内容 »
讨论   把此链接加入于...  与朋友分享   已已沉
添加到:                  |   书签  

There have been confirmed rumors[1] about Twitter planning to use Cassandra for a long time. But except the mentioned post, I couldn’t find any other references.

Twitter is fun by itself and we all know that NoSQL projects love Twitter. So, imagine how excited I was when after posting 更多相关的内容 »
讨论   把此链接加入于...  与朋友分享   已已沉
添加到:      1] about Twitter planning to use Cassandra for a long time. But except the mentioned post, I couldn’t find any other references.

Twitter is fun by itself and we all know that NoSQL projects love Twitter. So, imagine how excited I was when after posting ">            |   书签  

There is a dark side to most of the current NoSQL databases. People rarely talk about it. They talk about performance, about how easy schemaless databases are to use. About nice APIs. They are mostly developers and not operation and system administrators. No-one asks those. But it’s there where rubber hits the road.

The three problems no-one talks about – almost noone, I had a good talk with the Infinispan lead [1] – are: 更多相关的内容 »
讨论   把此链接加入于...  与朋友分享   已已沉
添加到:      Infinispan lead [1] – are:">            |   书签  

A lot of the problems we had to tackle in the last months were directly related to the data stores we used, as well as the schema of the objects we stored.

We’ve been using MySQL and Memcached from day one, because it’s always good when you have 50 different problems to tackle to use tools that you know (read 更多相关的内容 »
63 意见/ 评语   把此链接加入于...  与朋友分享   已已沉
添加到:      MySQL and Memcached from day one, because it’s always good when you have 50 different problems to tackle to use tools that you know (read ">            |   书签  

Data Store Overview

There are many current and emerging products that can be considered as suitable for storing and managing data. This list is an attempt to identify popular products that existing organizations that use MySQL may consider as alternative 更多相关的内容 »
讨论   把此链接加入于...  与朋友分享   已已沉
添加到:                  |   书签  

I've been playing recently with several distributed databases with the aim of choosing the best solution for my needs. Since there isn't much documentation on the web with a general overview on the subject, I write here some comments, thoughts and my humble experience. Hope it's usefull for you, this document is not a comparison of performance, or a "mine is bigger than yours",  just some ideas ;)

My background
Being my experience based on relatio 更多相关的内容 »
讨论   把此链接加入于...  与朋友分享   已已沉
添加到:                  |   书签  

Last week I ended up building a distributed keystore for a client. That wasn’t my original intention, but after doing testing on just about every project out there, it turned out to be the best (only?) solution for our needs.

Specifically, a production environment handling at least 100M items with an accelerating growth curve, very low latency retrievals, and the ability to handle 100s of inserts/s w/ variable-sized data (avg 1K, but up in many cases well beyond) … on EC2 更多相关的内容 »
讨论   把此链接加入于...  与朋友分享   已已沉
添加到:                  |   书签  

VoltDB launches Next-Generation Open-Source OLTP DBMS

Revolutionary open-source distributed DBMS eliminates price/performance and scalability barriers, keeps SQL and ACID

Billerica, Mass., May 25, 2010 – VoltDB, LLC, announced today the general availability of the VoltDB OLTP database management system (DBMS). Under the leadership of Postgres and Ingres co-founder, Mike St 更多相关的内容 »
21 意见/ 评语   把此链接加入于...  与朋友分享   已已沉
添加到:      VoltDB launches Next-Generation Open-Source OLTP DBMS

Revolutionary open-source distributed DBMS eliminates price/performance and scalability barriers, keeps SQL and ACID

Billerica, Mass., May 25, 2010 – VoltDB, LLC, announced today the general availability of the VoltDB OLTP database management system (DBMS). Under the leadership of Postgres and Ingres co-founder, Mike St">            |   书签  

Designing responsive web interfaces for analyzing short read data requires techniques to rapidly retrieve and display all details associated with a read. My own work on this has been relying heavily on Berkeley DB key/value databases. For example, an analysis will have key/value stores relating the read to aligned positions in the genome, counts of reads found in a sequencing run, and other associated metadata. < 更多相关的内容 »
讨论   把此链接加入于...  与朋友分享   已已沉
添加到:      Berkeley DB key/value databases. For example, an analysis will have key/value stores relating the read to aligned positions in the genome, counts of reads found in a sequencing run, and other associated metadata. <">            |   书签