The workload you originally described does not sound like a difficult
job for a relational database. Do you have any more information on the
specifics of your access patterns and where you feel that an RDBMS
might fall short?
-Nate
On Tue, Feb 23, 2010 at 11:27 PM, Cemal cemalettin@gmail.com
Hi,
Maybe I have to tell that we are very eager to evaluate NoSQL approaches and
for a simple case we want evaluate and compare each approaches.
In our case actually our data has not been denormalized yet and we are
suffering from a lot of joins. And because of very much updates in joined
tables
I found the following helpful:
http://www.rackspacecloud.com/blog/2009/11/09/nosql-ecosystem/
http://00f.net/2009/an-overview-of-modern-sql-free-databases/comments/507
http://cacm.acm.org/blogs/blog-cacm/50678-the-nosql-discussion-has-nothing-to-do-with-sql/fulltext
There is enough variation in
Cemal,
I've found the following analysis very helpful, it compares various noSQL
options and gives pros/cons of RDBMS vs noSQL:
No Relation: The Mixed Blessings of Non-Relational Databases by Ian Varley
http://ianvarley.com/UT/MR/Varley_MastersReport_Full_2009-08-07.pdf
-Alex
Hi all,
My question will be about appropriate NoSQL solution rather than asking
Cassandra related questions.
In our case:
- We have more than *denormalized* 4 million rows data and at the end of
this year we are expecting 5-6 million rows
- Every minute maybe more than 1000 rows can be
On Tue, Feb 23, 2010 at 3:54 PM, Chris Goffinet goffi...@digg.com wrote:
MySQL
Very funny! I assume this is related to MySQL's somewhat spotty record
of actually conforming to SQL standard, right? ;-D
(the NoSQL solution part)
-+ Tatu +-
I was not really expecting such an answer. :)
Any other idea?
On Wed, Feb 24, 2010 at 2:51 AM, Tatu Saloranta tsalora...@gmail.comwrote:
Very funny! I assume this is related to MySQL's somewhat spotty record
of actually conforming to SQL standard, right? ;-D
(the NoSQL solution part)
