3 ms·

In addition to that, I think the author is also conflating "model" vs "implementation". Some of the legacy relational databases are somewhat slow, but 1 TB of d

In addition to that, I think the author is also conflating "model" vs "implementation". Some of the legacy relational databases are somewhat slow, but 1 TB of data is hardly much even for something like PostgreSQL. The more sophisticated column-oriented databases and data warehouses would still be considered relational databases, and are much much faster (as I understand, for many applications, the primary downside of those is cost, rather than anything inherent in the relational model or the implementation). New, redesigned OLTP systems like VoltDB are also much faster than the original disk-based RDBMSs for transactional workloads.

dragontamer 12y ago
Heck, PostgreSQL 9.3 and above is consistently beating MongoDB in speed for instance. So Relational Databases can be (and often are) very fast databases. http://vibhorkumar.wordpress.com/2014/05/15/write-operation-mongodb-vs-postgresql-9-3-json/ http://vibhorkumar.wordpress.com/2014/05/15/write-operation-... I'm not an expert on the subject, but wasn't MapReduce the primary driver of NoSQL? Hadoop/HBase, etc. etc. Key-Value Store definitely (which has been mentioned), but even the most basic Key-Value store is more complicated than a glorified hash table.
- eigenrick 12y ago
  I love me some PG. :) There are a number of databases which are using unique storage models to achieve great numbers in circumstances for which their optimized (duh) DeepDB is an interesting one that is getting great throughput while running complex queries on incoming data. I believe they're using LSM Trees under the hood. I was definitely trying to avoid doing a survey of all of the products out there and what they're using (that would be a great article, though) I more wanted to make people cognizant of the models that they might encounter and why/how they're used. It was a bit ambitious to attempt that in a single article.

dragontamer 12y ago

Heck, PostgreSQL 9.3 and above is consistently beating MongoDB in speed for instance. So Relational Databases can be (and often are) very fast databases. http://vibhorkumar.wordpress.com/2014/05/15/write-operation-mongodb-vs-postgresql-9-3-json/ http://vibhorkumar.wordpress.com/2014/05/15/write-operation-... I'm not an expert on the subject, but wasn't MapReduce the primary driver of NoSQL? Hadoop/HBase, etc. etc. Key-Value Store definitely (which has been mentioned), but even the most basic Key-Value store is more complicated than a glorified hash table.

eigenrick 12y ago
I love me some PG. :) There are a number of databases which are using unique storage models to achieve great numbers in circumstances for which their optimized (duh) DeepDB is an interesting one that is getting great throughput while running complex queries on incoming data. I believe they're using LSM Trees under the hood. I was definitely trying to avoid doing a survey of all of the products out there and what they're using (that would be a great article, though) I more wanted to make people cognizant of the models that they might encounter and why/how they're used. It was a bit ambitious to attempt that in a single article.