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.
(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.)
(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.)