Manager, Software Engineering at a tech vendor with 10,001+ employees
Real User
Top 5
Aug 19, 2025
The platform should provide a UI feature where users have the ability to manage it. The CockroachDB platform should have a chatbot where users can inquire about pricing or seek solutions for queries, rather than relying on email support. The current UI only provides SQL playground, which is technical. There should be a UI playground where users with limited technical knowledge can run and update queries, similar to phpMyAdmin or Adminer. Latency optimization could be improved for globally distributed applications, particularly in query routing. For multi-region deployment, CockroachDB requires at least three plus replicas across data centers to achieve strong consistency across regions, which increases infrastructure costs including compute, storage, and networking. The disadvantages include cost-efficiency with multi-region deployment and schema migration speed, which should be faster compared to other drivers. The query optimizer should handle complex queries better through the UI interface.
I think the engine itself could be improved. If you miss a partition key, it should be able to be modeled. This is where AI could be really helpful. For example, if a user is from Australia, the system should know to look for their data there first instead of searching in the US or another continent.
Software Engineer at a consultancy with self employed
User
Nov 15, 2023
I find the serverless offer a bit confusing. The price is a function of the maximum database size. A single SELECT can use a number of request units, for example. If the throughput is high enough, you could run out of request units and be throttled if you do not pay attention to how your database is used.
The closer they can make CockroachDB to being completely compatible with Postgres, the better. It's almost compatible, but not completely. If it was, it would be nice to just be able to use Postgres libraries without any fiddling.
Executive Director / R&D Dept. General Manager at Riz Inc.
Real User
Jul 19, 2019
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.
CockroachDB is a high-performance, cloud-native database offering fault-tolerance, geo-partitioning, and PostgreSQL compatibility, ensuring distributed transactions with robust security for global applications.CockroachDB offers advanced features like geo-replication and ensures data residency through its distributed architecture. This minimizes application modifications by supporting the PostgreSQL wire protocol while providing enhanced fault-tolerance. High availability is maintained...
The platform should provide a UI feature where users have the ability to manage it. The CockroachDB platform should have a chatbot where users can inquire about pricing or seek solutions for queries, rather than relying on email support. The current UI only provides SQL playground, which is technical. There should be a UI playground where users with limited technical knowledge can run and update queries, similar to phpMyAdmin or Adminer. Latency optimization could be improved for globally distributed applications, particularly in query routing. For multi-region deployment, CockroachDB requires at least three plus replicas across data centers to achieve strong consistency across regions, which increases infrastructure costs including compute, storage, and networking. The disadvantages include cost-efficiency with multi-region deployment and schema migration speed, which should be faster compared to other drivers. The query optimizer should handle complex queries better through the UI interface.
I would like CockroachDB to have more compatibility with PostgreSQL, especially with the connection string and technical integrations.
I think the engine itself could be improved. If you miss a partition key, it should be able to be modeled. This is where AI could be really helpful. For example, if a user is from Australia, the system should know to look for their data there first instead of searching in the US or another continent.
I find the serverless offer a bit confusing. The price is a function of the maximum database size. A single SELECT can use a number of request units, for example. If the throughput is high enough, you could run out of request units and be throttled if you do not pay attention to how your database is used.
The initial setup and pricing could be improved.
The closer they can make CockroachDB to being completely compatible with Postgres, the better. It's almost compatible, but not completely. If it was, it would be nice to just be able to use Postgres libraries without any fiddling.
Cockroach does not support all types of protocols. I need to improve it myself to support a CouchDB on my network.
We are looking for more features to support distributed high availability and geo-partitioning.
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.