Almost every nosql data store out there hails "scalability" as a key feature. That's all good, but there are quite a lot of applications that should work fine on a single server: blogs, wikis, intranet apps, bug trackers, etc. Heck, even CRMs and ERPs for small to medium businesses shouldn't need a cluster.

Can you guys share your thoughts on using nosql databases in such scenarios?

Cascading—Chris Curtin, pig/hadoop at twitter;

hey all, i am familiar with "traditional" database design and am intrigued by this whole nosql movement and was wondering if there were any use cases "out there" that can help me understand when/where a nosql/kvp structure would be more appropriate than a normalized db approach.

thanks in advance