As I was reading about the problems this system needs to solve and the issues with Kyoto Tycoon, I thought that LMDB might be a good foundation for a solution. So I was gratified to find out that Quicksilver indeed uses LMDB. I gather Cloudflare has found that LMDB is indeed as reliable as it's advertised to be.<p>Looking forward to the eventual open-source release of Quicksilver.
I was working on something similar one year ago for a personal project.<p>I simply persisted the config in Mysql and synced the data to redis. Then each server had a redis replica locally to allow fast reads from OpenResty (nginx+lua scripts).<p>The project never took off, it was just an MVP. But why would someone pick Kyoto Tycoon instead?
The story of how they picked a storage engine ill-suited for their needs and then used ridiculous and unsustainable workarounds to deal with its shortcomings (including unsafe practices like relying on rebuilding the databases, assuming it’s safe to turn off synchronous writes for KV storage writes, etc) just confirms how shoddy engineering is at CloudFlare. That is peak technical debt.<p>(It’s one thing to make a wrong choice, it’s another to think you can paper over those mistakes and they’ll go away.)