Hot answers tagged nosql
4
Tens of terabytes of data in 3 tables sounds expensive in many ways.
Do you have budgetary constraints for this solution? Storing tens of terabytes of data in an in-memory NoSQL platform may be exactly what you're after, but it's likely to require dozens of servers.
You might get some good ideas from High Scalability. For example, it's interesting to see ...
3
This seems a little outside the scope of a StackExchange question. However.....
NoSQL databases are, typically, build to resolve specific issues with the relational model. The most common issue addressed is scalability. Are you planning to need to handle terabytes of data? However, because they're all designed to address different aspects of certain ...
3
There are a number of reasons not to use MongoDB as a pure key-value store, and there are some reasons to consider it. Mongo is optimized as a document store - it indexes all the fields in a document, and has rich primitives for JSON objects and hierarchies. You can use it as a key-value store, but the single-threaded nature means you won't be getting good ...
1
Are the performance gains from data consistency enough of a reason to develop in NoSQL, rather than relational?
I think your question presupposes a certain way of looking at things. Your fundamental tradeoff with NoSQL is a tradeoff between declarative ad hoc reporting and fast and loose inputs. This tradeoff is unacceptable for many (maybe most) ...
Only top voted, non community-wiki answers of a minimum length are eligible
