2 ms·
Can someone explain the inner workings and thus tradeoffs it makes? And how it would impact when and how you'd want to use it?
by didibus 9y ago
Can someone explain the inner workings and thus tradeoffs it makes? And how it would impact when and how you'd want to use it?
- tshannon 9y agoThe FAQ on the website is a good place to start: https://www.cockroachlabs.com/docs/stable/frequently-asked-questions.html https://www.cockroachlabs.com/docs/stable/frequently-asked-q... When is CockroachDB a good choice? CockroachDB is well suited for applications that require reliable, available, and correct data regardless of scale. It is built to automatically replicate, rebalance, and recover with minimal configuration and operational overhead. Specific use cases include: Distributed or replicated OLTP Multi-datacenter deployments Multi-region deployments Cloud migrations Cloud-native infrastructure initiatives When is CockroachDB not a good choice? CockroachDB is not a good choice when very low latency reads and writes are critical; use an in-memory database instead. Also, CockroachDB is not yet suitable for: Heavy analytics / OLAP
- didibus 9y agoI guess I was hoping for the engineering expert FAQ. What level of reliability, how, what tradeoff in my table design will I need to make, same thing for availability, correctness and scale. None of the info in this FAQ allow me to know that CockroachDB is the right choice for me against the competition which advertises the same generic DB marketing terms. Edit: And yes, I can go and read the documentation and deep dive into the internals myself, but I don't care enough to do so, because I already have DBs that fulfill those use cases that I know off, and I would hope therefore that CockroachDB would make it very quick, easy and in my face to find the info that will make me go: Ah Ha, this is the distinguishing factor and the reason why I might want to favor and care to use CockroachDB the next time I've got such a use case.