We compared CockroachDB and YugabyteDB several years ago and had consistently better performance with YugabyteDB. We recently migrated our workloads from self-h

We compared CockroachDB and YugabyteDB several years ago and had consistently better performance with YugabyteDB. We recently migrated our workloads from self-hosted to YugabyteDB Managed and have been happy. We do thousands of queries per second with less than 5ms latency. I would say the biggest problem we've had is managing Postgres connection memory usage but the Yugabyte team is working on a server-side proxy similar to pgBouncer but without the same limitations [1]. We're also awaiting the release of CDC that doesn't require us to run Kafka. While for other companies Kafka might already be a dependency in their stack, it's not for us and we'd prefer not to introduce it just for CDC. Their Managed platform handles backup/restore, encryption, SSL, metrics, upgrades, and one-click scaling. You can even configure multi-region clusters with read replicas. Their platform is not very flexible with compute, however. You have fixed CPU and RAM sizes to choose from. Happy to answer specific questions. [1] https://docs.yugabyte.com/preview/explore/connection-manager/connection-mgr-ysql/ https://docs.yugabyte.com/preview/explore/connection-manager...