when you show me a full up - for 10,000 users - payroll system, HR system, a time and attendance system, a <long list of applications, useful ones - beyond say facebook...> written with an EAV
I'll start looking for another job.
and they talk about having to scale in a single (hardware/host) server - we are not encumbered by that limitation.
Funny that they write:
... This new kind of database management system is commonly called a key/value store. In fact, no official name yet exists ...
no official name yet exists, another case of someone 'inventing' the EAV for the 'first' time (I remember the first time I invented it!)
http://asktom.oracle.com/Misc/this-should-be-fun-to-watch.html The EAV model has very limited focus/use - it is very useful in a very specific type of application.
But to ask general questions of it - no, it does not work, "to scale" is not part of it's vernacular.
I love their picture of a car on page 2
http://www.readwriteweb.com/archives/is_the_relational_database_doomed.php?p=2 umm, how is that different from
create table car(
silly_id number primary key,
make,
model
color,
year )
Ok, this is annoying:
<quote>
Suitability for Clouds
The first benefit is that they are simple and thus scale much better than today's relational databases. If you are putting together a system in-house and intend to throw dozens or hundreds of servers behind your data store to cope with what you expect will be a massive demand in scale, then consider a key/value store.
Because key/value databases easily and dynamically scale, they are also the database of choice for vendors who provide a multi-user, web services platform data store. The database provides a relatively cheap data store platform with massive potential to scale. Users typically only pay for what they use, but their usage can increase as their needs increase. Meanwhile, the vendor can scale the platform dynamically based on the total user load, with little limitation on the entire platform's size.</quote>
they are simple
THUS
they scale
HUH? BOING? Wait WHAT?
they are simple, therefore they scale.
read that to yourself over and over and over again.
they are simple, hence we say they shall scale.
Fascinating.
Too bad it is, well, not factually accurate.
But, the article is not entirely incorrect, this is well said:
<quote>
Key/Value Stores: The Bad
The inherent constraints of a relational database ensure that data at the lowest level have integrity. Data that violate integrity constraints cannot physically be entered into the database. These constraints don't exist in a key/value database, so the responsibility for ensuring data integrity falls entirely to the application. But application code often carries bugs. Bugs in a properly designed relational database usually don't lead to data integrity issues; bugs in a key/value database, however, quite easily lead to data integrity issues.
</quote>
When my paycheck is produced or producable by a one of these systems on a grand scale.... I'll be right there.