I 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 avail

I 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.