3 ms·
So true, I often see people choose a database without considering pros and cons, they often considering only what they want as a developer to work with or to tr
by zihotki 10y ago
So true, I often see people choose a database without considering pros and cons, they often considering only what they want as a developer to work with or to try and don't consider the nature of the data. Time series data fits the best in Cassandra and some other column-oriented DBs but definitely not in MongoDB.
- threeseed 10y agoTime series data is actually a great fit for MongoDB. You create a collection for each measurement, JSON document for each day and then preallocate the fields for each hour/minute/second. With batching you can update 100K documents a second pretty easily off one node. For example: https://blog.serverdensity.com/using-mongodb-as-a-time-series-database/ https://blog.serverdensity.com/using-mongodb-as-a-time-serie...