> Safe: Implemented in Rust programming language and using Tokio runtime ensures memory and thread safety.
Does memcached have issues with memory and thread safety? I've never heard of them if it does.
> Fast: Can process thousands of requests with minimal overhead.
For a network cache you want _predictable_ performance more than "fast" performance, so that you're able to predict how a system will scale. "Fast" is among the top priorities for choosing a network cache implementation.
> Compatible: memc.rs is 100% compatible with memcached binary protocol. No need to rewrite your code. Just start a server and use your favorite language/framework.
What about tools for monitoring memcached in production? Does it support consistent hashing across a pool memcached servers?
Ultimately: why?