| I've never heard of Dragonfly before this, and I see it's a Redis competitor, but the examples here really stretch the definition of what it means to be "not boring." > how your junior team member ran "flushdb" in production and caused your service traffic to stall FLUSHDB removes all keys from the database which, depending on your application, could indeed cause a lot of problems. But this seems pretty boring to me: the "delete all data" command deletes all data. Yes, the consequences of doing this on a production application are going to make sure someone's writing a COE, but this doesn't strike me as anything unexpected. edit: This might be more about sync deletes causing outages, but it's really pick your poison here. Which is less boring, "I ran delete and the database locked" or "I ran delete and did a read but the data was still there?" Really up to you. > how your engineering team spent a month tuning the Redis engine before Christmas "Boring" doesn't mean "not tunable" or "one-size-fits-all." MySQL and Postgres are two relatively ancient databases that most people would consider to be really boring, yet they have endless options for performance tuning. Even in todays cloud-first devops-first era, people still make a living off being DBAs, where tuning these systems is their primary job. If anything, I would be much more wary of a system where the configuration isn't exposed to the user, and the engine uses some heuristics to figure operating parameters out without any way to tweak it. To me, that seems a lot less "boring." |