Menu
I'm working on an application that I'm going to write with C and i am considering to use a nosql db for storing timeseries data with at most 8 or 9 fields. But in every 5 minutes there will huge write operations such as 2-10 million rows and then there will be reads(but performance is not as crucial in read as in the write operation).
I'm considering to use a NoSQL db here in order to store the data but couldn't decide on which one to use. Couchdb seems to have a stable driver called pillowtalk for C; but Mongo's driver doesn't look as promising as pillowtalk. I'm also open to other suggestions.
What is your recommendation?
841
If you are required to perform complex and dynamic querying and reporting, then you should avoid using NoSQL as it has a limited query functionality. For such requirements, you should prefer SQL only. NoSQL also lacks in the ability to perform dynamic operations. It can't guarantee ACID properties.
MongoDB Advantages and Use CasesMongoDB is a schema-less database and stores data as JSON-like documents (binary JSON). This provides flexibility and agility in the type of records that can be stored, and even the fields can vary from one document to the other.
Hence, the choice between the two depends on how you plan on querying the data. If the required data can be accessed using a single Primary Key, Apache Cassandra would be suitable but if more complex queries to extract specific values in dynamic data is required, MongoDB should be preferred.
For crazy performance contraints you can't beat Tokyo Cabinet: http://fallabs.com/tokyocabinet/
There is also a server component called Tokyo Tyrant which looks really cool.
134
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
