4 ms·
Along with the other reasons, Badger is not that great. When you have the funding and presumably the developers they have, it makes sense to do something bette
by CheezeIt 5y ago
Along with the other reasons, Badger is not that great. When you have the funding and presumably the developers they have, it makes sense to do something better.
- eatonphil 5y agoAnywhere I can read more about issues with Badger?
- srcreigh 5y agoNever used badger but after discovering major perf issues in graphene graphql library for python, the issue tracker is sometimes a good place to look. I found this one pretty quickly: https://discuss.dgraph.io/t/db-write-latency-in-badgerdb-high-when-the-size-of-the-data-increases-exponentially/16192/5 https://discuss.dgraph.io/t/db-write-latency-in-badgerdb-hig...
- CheezeIt 5y agoIts issue trackers. There have been sad bugs going on years deep into the project. Maybe they’re all mopped up in 2022 but I wouldn’t count on it. Its design does well on a certain usage profile at the expense of mixed read/write or other workloads. Cockroach has more money and could throw better developers (more experienced) at the problem. Haven’t looked at Pebble though.