3 ms·
I always feel a little weird using memcached because it has never once crashed on us but when it goes down we have a bad time with circuit breakers. We only ha
by hinkley 3y ago
I always feel a little weird using memcached because it has never once crashed on us but when it goes down we have a bad time with circuit breakers.
We only have problems with memcached when we create them ourselves. Disk backing store would soften that considerably.
- lanstin 3y agomemcached type API with RocksDB backing store is pretty good. Honestly, at this point hasn't every one written some in memory DB with various methods to persist and various consistency models as a result? At this point the magic is in client routing to the appropriate shard without having to redeploy to change the shard configuration and to allow multi-remote callers to access the data and still get access without disk load or mutex/locking around the data. I have a thing where the shards each have sub-shards in process and 1 go-routine per sub shard; communication to/from the remote callers is via channels to a per-request go-routine (or whatever it is gRPC does) and the main subs hard go-routine has no locking on itself. Just a big hash map and a DLL to implement an LRU so I have a hard cap on memory usage, and no allocations for lookups or mutations (just creations).