gps - What kind of NoSQL storage should we use?

Question

We are a IoT company that provide services for transportation and logistics companies. As a infrastructure service provider we offer GPS tracking devices to our client.

Although the format of GPS tracking data is very neat (gpsId, longitude, latitude, speed, direction, reportTime, etc), but amount of it is very big. Every device report GPS tracking information per 10 seconds, and we have 100k devices, thus 60*60*24*100000/10 = 864M rows of new data generated every day.

Using the data collected by GPS tracking device of a particular vehicle, client can review the traces of this vehicle within a given time period (for example, last 10 days, will need 60*60*24*10/10 = 86.4K rows of data).

Currently we use MySQL as storage medium, and take advantage of sharding and table partitioning(based on gpsId) of it. But since the data is so big and query on it is so frequent, so I wonder if we can use a NoSQL storage to fit this scenario better?

Historical data is also useful for data analysis.

Appreciated.

Answer 1

听起来你想要一个时间序列数据库。这些数据库针对按时间索引的大型数字数组进行了优化。维基百科列出了几个用于时间序列的开源和专有数据库，包括几个建立在 Cassandra 之上的数据库。

时间序列数据库的维基百科条目

Answer 2

为什么要选择 NoSQL？您可以在 MySQL 中有效地存储地理位置数据 -阅读此内容。

有关其他数据库选项，请阅读此。