6 ms·

Out of curiosity, why write https://github.com/cockroachdb/pebble https://github.com/cockroachdb/pebble and not just use https://github.com/dgraph-io/badger htt

Out of curiosity, why write https://github.com/cockroachdb/pebble https://github.com/cockroachdb/pebble and not just use https://github.com/dgraph-io/badger https://github.com/dgraph-io/badger?

gleenn 5y ago
Well it says its SQL, not just a KV-store. That's a pretty ig difference to start.
- eatonphil 5y ago
  Hmm? The pebble page doesn't say anything about SQL. It just says KV like Badger.
  - gleenn 5y ago
    Did you miss the title? It literally says SQL in the title.
    - CheezeIt 5y ago
      Pebble is a key-value store, not an SQL database.
    - eatonphil 5y ago
      No I don't see that either. document.title on the pebble Github page says: 'cockroachdb/pebble: RocksDB/LevelDB inspired key-value database in Go'
    - swasheck 5y ago
      in the article: CockroachDB (or CRDB for short) consists of a distributed SQL layer on top of a distributed key-value store.
      - detaro 5y ago
        ... and the question was about why they built the key-value store instead of using an existing one. The question clearly was about pebble, not CockroachDB, so why are you arguing about what CockroachDB is?
        swasheck 5y ago
        i’m not arguing anything. there was confusion about SQL being in the title and the storage being KV. so i was trying to relay information that may advance the conversation.
        detaro 5y ago
        My bad, got commenters mixed up.
- deleted 5y ago
  [deleted]
DenseComet 5y ago
A big reason seemed to be compatibility with the RocksDB on-disk file format. https://www.cockroachlabs.com/blog/pebble-rocksdb-kv-store/ https://www.cockroachlabs.com/blog/pebble-rocksdb-kv-store/
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 ago
  Anywhere I can read more about issues with Badger?
  - srcreigh 5y ago
    Never 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 ago
    Its 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.

Out of curiosity, why write https://github.com/cockroachdb/pebble https://github.com/cockroachdb/pebble and not just use https://github.com/dgraph-io/badger https://github.com/dgraph-io/badger?

gleenn 5y ago

Well it says its SQL, not just a KV-store. That's a pretty ig difference to start.

eatonphil 5y ago
Hmm? The pebble page doesn't say anything about SQL. It just says KV like Badger.
- gleenn 5y ago
  Did you miss the title? It literally says SQL in the title.
  - CheezeIt 5y ago
    Pebble is a key-value store, not an SQL database.
  - eatonphil 5y ago
    No I don't see that either. document.title on the pebble Github page says: 'cockroachdb/pebble: RocksDB/LevelDB inspired key-value database in Go'
  - swasheck 5y ago
    in the article: CockroachDB (or CRDB for short) consists of a distributed SQL layer on top of a distributed key-value store.
    - detaro 5y ago
      ... and the question was about why they built the key-value store instead of using an existing one. The question clearly was about pebble, not CockroachDB, so why are you arguing about what CockroachDB is?
      - swasheck 5y ago
        i’m not arguing anything. there was confusion about SQL being in the title and the storage being KV. so i was trying to relay information that may advance the conversation.
        detaro 5y ago
        My bad, got commenters mixed up.
deleted 5y ago
[deleted]

DenseComet 5y ago

A big reason seemed to be compatibility with the RocksDB on-disk file format. https://www.cockroachlabs.com/blog/pebble-rocksdb-kv-store/ https://www.cockroachlabs.com/blog/pebble-rocksdb-kv-store/

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 ago
Anywhere I can read more about issues with Badger?
- srcreigh 5y ago
  Never 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 ago
  Its 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.