When I reviewed YugaByteDB 1.0 in 2018 it combined distributed ACID transactions multi-region deployment and support for Cassandra and Redis APIs. At the time PostgreSQL support was ’on the way’ signification incomplete and barely tested. Fast advanced to May 2022 and the Postgres train has pulled into the standing.
YugaByteDB 1.0 was built on top of an enhanced fork of the RocksDB key-value store. It used a log-structured key-to-document storage engine had a pluggable API layer used Raft for bunch consensus and used mixed close clock (HLC) timestamps and Network Time Protocol (NTP) clock synchronization for node time synchronization. Only the core functionality of YugaByteDB 1.0 was open rise; I reviewed an enterprise rendering that included proprietary pieces such as the YugaWare orchestration layer.
Currently in YugabyteDB 2.13 the PostgreSQL support is perfectly advanced (but not fully done). The fruit is now entirely open rise (Apache 2.0) although enterprises can (and do) buy a support contract for the Kubernetes-based Yugabyte Platform and anyone can form paid bunchs on the Yugabyte Cloud that run on Amazon Web Services (AWS) or Google Cloud Platform (GCP). Anyone can also form a free two-CPU one-node ’bunch’ on the Yugabyte Cloud for exploration purposes. At this point more than a million YugabyteDB bunchs have been deployed.
YugabyteDB straightly competes with other distributed SQL transactional databases such as Google Cloud Spanner Amazon Aurora and CockroachDB. To a lesser degree it also competes with transmitted transactional databases such as Oracle Database SQL Server and IBM DB2 as nation move their database loads to the cloud and shift their application architectures to microservices.