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
Top 10
2023-11-15T14:41:00Z
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
2019-07-19T10:23:00Z
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 distributed SQL database built on a transactional and strongly-consistent key-value store. It scales horizontally; survives disk, machine, rack, and even datacenter failures with minimal latency disruption and no manual intervention; supports strongly-consistent ACID transactions; and provides a familiar SQL API for structuring, manipulating, and querying data.
CockroachDB is inspired by...
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.