
Evaluation: YugabyteDB does PostgreSQL proud
After I reviewed YugaByteDB 1.0 in 2018, it mixed distributed ACID transactions, multi-region deployment, and help for Cassandra and Redis APIs. On the time, PostgreSQL help was “on the best way,” which means incomplete and barely examined. Quick ahead to Could 2022, and the Postgres practice has pulled into the station.
YugaByteDB 1.0 was constructed on high of an enhanced fork of the RocksDB key-value retailer. It used a log-structured, key-to-document storage engine, had a pluggable API layer, used Raft for cluster consensus, and used hybrid logical clock (HLC) timestamps and Community Time Protocol (NTP) clock synchronization for node time synchronization. Solely the core performance of YugaByteDB 1.0 was open supply; I reviewed an enterprise model that included proprietary items, such because the YugaWare orchestration layer.
At present, in YugabyteDB 2.13, the PostgreSQL help is kind of superior (however not utterly performed). The product is now solely open supply (Apache 2.0), though enterprises can (and do) purchase a help contract for the Kubernetes-based Yugabyte Platform, and anybody can create paid clusters on the Yugabyte Cloud that run on Amazon Internet Providers (AWS) or Google Cloud Platform (GCP). Anybody can even create a free two-CPU one-node “cluster” on the Yugabyte Cloud for exploration functions. At this level greater than one million YugabyteDB clusters have been deployed.
YugabyteDB immediately competes with different distributed SQL transactional databases, similar to Google Cloud Spanner, Amazon Aurora, and CockroachDB. To a lesser extent, it additionally competes with conventional transactional databases, similar to Oracle Database, SQL Server, and IBM DB2, as folks transfer their database masses to the cloud and shift their software architectures to microservices.