[ksec]

>Redis, which I'd like to call the "original" key/value store

My old friend Memcached just came by and want to say Hello. He is still alive and kicking. Netflix has been treating him well.

[scns]

There is a 100% binary protocol compatible implementation in Rust.

https://memc.rs/intro

[lapser]

Wow! I was under the very wrong impression that memcached hadn't been updated in a long time. It has been having regular releases for longer than I thought. Great to hear!

[ksec]

Somewhere along the ling, lots of ( well deserved ) hype went to Redis and Postgres, and people thought Memcached and MySQL died.

I have been wondering for a long time if we will ever see Memcached 2.0 and MySQL 9.0

[lazyjones]

Memcached isn't even a "key/value" store (in database terms), it's a cache.

https://github.com/memcached/memcached/wiki/ProgrammingFAQ#w...

[blagie]

My major use-case for a KVS is *reliable, scalable* storage. RDBMS has an upper bound on scaleability. Removing the relational component removes a lot of power and flexibility, but improves performance and scalability.

That's often a good choice!

A KVS can be arbitrarily horizontally scaleable. That might not sound necessary for a small project, but even there:

1. You can deal with big data (e.g. keystroke-level event data, etc.)

2. You don't have to worry about scaleability. It's one less thing to worry about.

3. You're set up for success if you take the unicorn route.

That's not memcached. I like memcached, but it's not the same as a KVS.

[zeckalpha]

It has cache in the name so people are less likely to use it inappropriately.

[johnwoods]

> My old friend Memcached just came by and want to say Hello. He is still alive and kicking. Netflix has been treating him well.

Forgot my dear buddy. Added it back.

[inferiorhuman]

BerkeleyDB's been around since the mid-90s…