CockroachDB Reviews

I use CockroachDB to test big data samples and to create the best structure for databases. We have four users and required 10 people for deployment and maintenance. 

Cockroach does not support all types of protocols. I need to improve it myself to support a CouchDB on my network.

I have been using this solution for two years. 

This is a stable solutions, although we have experienced some issues with the many protocols we need to follow. 

The customer service and support for this solution is not very good. 

The initial setup was straightforward. It took one week to deploy. 

 I would rate this solution a nine out of ten. 

The solution is used for Kubernetes to put on database. 

The availability and the easy to use feature is the most valuable. The documentation is also good. 

The initial setup and pricing could be improved. 

I have experience with CockroachDB.

It is a stable solution.I would rate the stability a nine out of ten.  

It is a scalable solution. I would late the scalability a nine out of ten. 

Previously, I have used Postgres but the operator for Postgres is not very good and that is why we shifted to CockroachDB.

The initial setup of CockroachDB can be difficult initially if you are pushing on the operator line but then it becomes easy. Only one person is required for the maintenance of any project on CockroachDB.

We are using the Helm. So we do the the upgrade and the deployment of the cockroach by ourselves.

The pricing is good but can be made cheaper. I would rate the pricing a five out of ten. 

The advice of just to read the documentation and look for examples. I would rate the overall solution an eight out of ten. 

We are currently evaluating this product to see if it can support distributed transactions with high availability. We are comparing it with Oracle, trying to see it can achieve the same thing.

The initial setup and deployment are simple.

We are looking for more features to support distributed high availability and geo-partitioning.

I have been working with CockroachDB for close to six months.

We are still evaluating and I have only used a small amount of data. For a small volume, the stability seems perfectly fine. As for when the volume of data grows, this is something that I will have to check.

We have not tested scalability.

We are in touch with a couple of vendors from Cockroach Labs and the technical support is good.

We use a combination of cloud-based and on-premises databases. On-premises we have Oracle and SQL Server. Our cloud-native databases are PostgreSQL and MySQL.

PostgreSQL is quite similar to Oracle but CockroachDB is still evolving.

The initial setup is not complex.

At this point, I have not used this product enough to fully rate it on all of the features. In three or four months' time, I will have a better idea and understanding of it.

I would rate this solution a six out of ten.

The use case is a backend DB for an app.

The CockrorchDB is on CentOS7.x with a cloud server service.

CockroachDB is a best practice for my organization.

High management of the CockroachDB (like creating or managing a data center across regions) seems so simple, and users can focus on developing the app.

CockroachDB is very handy.

I think CockroachDB has two important valuable features which are my favorite:

1. Having high fault-tolerance for clusters level and even data center level, which may run by a simple process.

2. The learning curb was low (for me at least). This comes into play for installing, deployment, SQL and more.

I think that this DB is helpful to easily and speedily provide a single and large service to the world.

As additional features, I wish there was Japanese documentation, instead of just English. I know how powerful and simple CockroachDB can be for many Japanese people with the correct documentation.

Half a year