Re:Drop-In Replacement for Memcached
by lumost on Sunday December 12, 2021 @04:00PM
(#29533558)
Biggest value prop seems to be that it's a single binary built off cargo, and that it's rust based. I wouldn't be surprised to see “single binary” become a selling point for container based shops even if all else is equal.
[ Parent
| on HN ]
AFAIK, memcached's only mandatory external dependency is libevent. And you can statically link that if you want.
Soon we'll see entire docker compose stack packed into single binary and everything will go back again
It's pretty convenient options for local dev. I am working on a project that has 7 services but they can be bundled into a single binary that has all 7 and NATS packaged in (plus you can spin up multiple instances of the services). Very convenient and builds in a few seconds.
Re:Drop-In Replacement for Memcached
by aledalgrande on Sunday December 12, 2021 @07:19PM
(#29535163)
And after a few years, "modular architecture with dynamically linked libraries! lean binaries!"
Unless you're doing something very special, I'd guess that most container based solution will just get the memcached Docker image on Docker Hub. There's very little to be gained by building your own memcached image, with a "single binary" alternative.