Using its geofencing, which is awesome! Not ready for prod yet, and I'll open-source the code;
I started building a generic geofence gRPC framework on top of tile38. You get a gRPC service that abstracts away the Redis API from you, and is generic enough to run multiple applications from the same tile38 server. It works by namespacing keys into their own collection. The namespacing is done through authentication with the header metadata, so it becomes transparent to the gRPC client.
I'm
* sending a notification every time the bus is x km/miles from someone (static geofences),
* triggering certain actions when user's at a train station (in conjunction with Google/Android geofencing)
I have been trying to use roaming geofences, but don't really have much use for them at the moment.
I started building a generic geofence gRPC framework on top of tile38. You get a gRPC service that abstracts away the Redis API from you, and is generic enough to run multiple applications from the same tile38 server. It works by namespacing keys into their own collection. The namespacing is done through authentication with the header metadata, so it becomes transparent to the gRPC client.
I'm
* sending a notification every time the bus is x km/miles from someone (static geofences), * triggering certain actions when user's at a train station (in conjunction with Google/Android geofencing)
I have been trying to use roaming geofences, but don't really have much use for them at the moment.