What should be the considerations for choosing SQL/NoSQL?
Posted
by Yuval A
on Stack Overflow
See other posts from Stack Overflow
or by Yuval A
Published on 2010-03-13T21:22:18Z
Indexed on
2010/03/13
21:25 UTC
Read the original article
Hit count: 345
Target application is a medium-sized website built to support several hundred-thousand users an hour, with an option to scale above that. Data model is rather simple, and caching potential is pretty high (~10:1 ratio of read to edit actions).
What should be the considerations when coming to choose between a relational, SQL-based datastore to a NoSQL option (such as HBase and Cassandra)?
© Stack Overflow or respective owner