5 ms·

(crdb eng) I'm not sure what "document DB" means here, mind elaborating?

• aPoCoMiLogin 5y ago
  he is probably referring to the docdb document store in yugabyte: https://docs.yugabyte.com/latest/architecture/layered-architecture/#docdb https://docs.yugabyte.com/latest/architecture/layered-archit...
  • motives 5y ago
    Indeed I was referring to yugabyte, apologies for the clumsy phrasing, I havent used crdb but I guess it is a postgres frontend layered on a KV store instead of a document store?
    • qeternity 5y ago
      As opposed to? Postgres is “just” a Postgres front end on top of a kv store.
      • anarazel 5y ago
        I don't think that's really true. Which part of postgres would you describe as a KV store, compared to what cockroach does with RocksDB?
    • manigandham 5y ago
      Yugabyte uses actual Postgres code for the query layer, on top of data persistence (distribution/replication) handled by DocDB document store, which itself is a layer on top of RocksDB: https://blog.yugabyte.com/how-we-built-a-high-performance-document-store-on-rocksdb/ https://blog.yugabyte.com/how-we-built-a-high-performance-do... CockroachDB (aka CRDB) is completely custom and compatible with Postgres wire/datatype protocols, which operates directly on its own key/value store called Pebble (but originally was also RocksDB): https://www.cockroachlabs.com/blog/distributed-sql-key-value-store/ https://www.cockroachlabs.com/blog/distributed-sql-key-value... Both systems are foundationally the same SQL-on-KV but implement it very differently.