redcon

Hello, there is an excellent library for golang which allows you to implement the redis server protocol: https://github.com/tidwall/redcon I would like to put in the effort to implement most redis commands there and map them to SQL, so that all data can be saved inside a fine tuned sqlite. Essentially if this is implemented we would have a database compatible to redis, the difference is that data is saved to disk and not to RAM. Is there a use case for that? Do people want that? There is some interesting things that could be done with that but I am not sure if the world needs this.

> how many simultaneous concurrent (client) connections does this support? The client connections are very lightweight. The protocol library is based on https://github.com/tidwall/redcon. I don't have exact numbers but this link may be helpful (which compares Redcon to Redis): https://simongui.github.io/2016/10/24/benchmarking-go-redis-.... I've seen it handle 16K+ client connection without issue, but typically a client library that supports pooling should be used (like Redigo). > how many simultaneous moving objects and at what update frequency? Depends on the complexity of the objects, the number of nearby objects, and the server hardware. Each collection of objects consists of one btree and one rtree for key/id lookups and spatial queries respectively. So updating a single point is like O(log(n)+log(m)). An in-memory database like Tile