10 ms·
CockroachDB: The Resilient Geo-Distributed SQL Database
- noncoml 5y agoOut 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 agoWell it says its SQL, not just a KV-store. That's a pretty ig difference to start.
- eatonphil 5y agoHmm? The pebble page doesn't say anything about SQL. It just says KV like Badger.
- gleenn 5y agoDid you miss the title? It literally says SQL in the title.
- CheezeIt 5y agoPebble is a key-value store, not an SQL database.
- eatonphil 5y agoNo 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 agoin 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?
- deleted 5y ago[deleted]
- DenseComet 5y agoA 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 agoAlong 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.
- traceroute66 5y agoThe CockroachDB team are doing great work no doubt, but I wish they'd stop leaning on the whole "Postgres compatible" thing. Its not and there's no clear roadmap for it to be. I'm not talking about obscure edge-case stuff here, I'm talking about some pretty major low-hanging fruit that is there is Postgres and not there in CockroachDB. Anyone who thinks they can magically drop Postgres for Cockroach will be sorely disappointed. And yes I've raised it with CockroachDB salesdroids when they've "reached out" and all I get in return is the digital equivalent of a shoulder shrug.
- gizmodo59 5y agoI often see these “I raised this to sales team… but they are not listening”. The cost of the sales team (including sales engineers) working on an opportunity is not low. If you have a use case and explain to them how you want to use their product (and if you are serious enough to buy it at the end of evaluation if it satisfies your requirements. You must also have influence in your company to make decisions. Some random startup with little cash to spend on software is not going to get you far) then they will surely try to address each of your specific issues. If not they may tell you it’s not a good use case. Just saying something about compatibility doesn’t really give them (or any Enterprise software vendor) to really hear you. This is not to say all companies are like that but that’s how it works in general in enterprise software. Every conversation is part of a Salesforce stage (whether we like it or not)
- RedShift1 5y ago> If not they may tell you it’s not a good use case. That may is key here. I've never had a sales guy say ok this doesn't fit. They will go to great lengths to fit their square peg into your round hole.
- gizmodo59 5y agoThat’s the job of sales engineer too in many cases. But a good account executive will tell you upfront if it’s not a good use case. If not you won’t buy at the end of evaluation and that has consequences for them (Companies need to predict quarterly revenues and by betting on a bad use case that person will have a bad projection of sales for that quarter or year which will ultimately be bad for them)
- mnming 5y agoI really hope CockroachDB can continue to hire engineers from Australia. Would be one of the best companies to work for in the whole APAC region.
- infogulch 5y agoI wonder if they intend to open source the serverless model once it comes out of beta. Seems like an ideal model to run a multi tenant service.
- etaioinshrdlu 5y agoHas anyone used Django with cockroachdb successfully? Are there major problems with migrations due to table alters being asynchronous? Also, is the OLAP performance really that bad?
- skyde 5y agoto be fair the open source version does not support geo replication!