We are doing some R&D related to tracking objects. For example, let's say we need to track vehicles & plot it's path on a map in real-time. In addition the coordinates will have to be saved to the DB so we can re-call the paths. We think this is similar to a chat application where;
1) Interested parties will login in & SUBSCRIBE to a channel (say RoomX)
2) Vehicles will PUBLISH it's location lat/long to RoomX
3) When new data point (lat/long) gets to RoomX, new coordinates get published to others who have subscribed to RoomX. At client app, we can plot the path based on the receiving lat/long
4) At the server incoming lat/long data will get persist so that we can re-call the path a vehicle took at any given time/date
Vehicles will publish it's locations based on it's speed (ex:- if it's moving slow, lat/long will be sent every 10 seconds, but if it's moving fast lat/long data will be sent every second)
We think Redis pub/sub model is ideal for this situation. But if there are 1000+ vehicles constantly on the move and there are lot of parties subscribed to channels, how well Redis will handle incoming data load? I couldn't find any performance statistics for a similar use case.
I have read about geospatial related techs. which I haven't started to R&D. So I am not sure how useful they are for this use case.
Expert thoughts are appreciated.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
To post to this group, send email to redi...@googlegroups.com.
Visit this group at http://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.