Recently developed a project, the vehicles will be back to coordinate data real-time transmission, so that after the query path information,
Could you tell me how to design a database to, in order to solve the problem of large amount of data,
It is difficult to exactly like how data to one day,,, or have questions I didn't think
Consult modestly,

CodePudding user response:

Without the transaction, without relevance table, simple data structure, HBase

CodePudding user response:

If you must use a relational database, consider according to vehicle number hash depots

Can write data back through the message middleware such as kafka buffer

CodePudding user response:

Relational data only for the final coordinates, process data using mongo, a car one table, one day a record, a record list of coordinates, a list of additional real-time coordinate; Easy to read, write and convenient,


Using relational database, can also be done similar project, 5 ~ 10 seconds, a record, but the machine up to 200 units, each machine table; Data growth is faster, it is necessary to control the life cycle of data; Such as in previous years, the data backup to cold storage,

CodePudding user response:

Still have to watch carefully, I wonder if I can use time depots

CodePudding user response:

refer to the second floor will respond to the heavy rain:

if you have to use a relational database, consider according to vehicle number hash depots

Can write data back through the message middleware such as kafka buffer

Factor is too much, have to digest