When I reviewed YugaByteDB 1. in 2018, it blended distributed ACID transactions, multi-location deployment, and assist for Cassandra and Redis APIs. At the time, PostgreSQL assist was “on the way,” that means incomplete and hardly examined. Speedy forward to Could 2022, and the Postgres teach has pulled into the station.
YugaByteDB 1. was built on top rated of an enhanced fork of the RocksDB crucial-value keep. It applied a log-structured, important-to-document storage motor, experienced a pluggable API layer, used Raft for cluster consensus, and utilized hybrid reasonable clock (HLC) timestamps and Community Time Protocol (NTP) clock synchronization for node time synchronization. Only the core features of YugaByteDB 1. was open resource I reviewed an company variation that bundled proprietary parts, these types of as the YugaWare orchestration layer.
Presently, in YugabyteDB 2.13, the PostgreSQL assistance is pretty highly developed (but not fully performed). The merchandise is now solely open up resource (Apache 2.), whilst enterprises can (and do) invest in a assistance contract for the Kubernetes-dependent Yugabyte System, and any person can develop compensated clusters on the Yugabyte Cloud that run on Amazon Internet Products and services (AWS) or Google Cloud Platform (GCP). Any individual can also produce a cost-free two-CPU a person-node “cluster” on the Yugabyte Cloud for exploration reasons. At this issue more than a million YugabyteDB clusters have been deployed.
YugabyteDB instantly competes with other dispersed SQL transactional databases, these kinds of as Google Cloud Spanner, Amazon Aurora, and CockroachDB. To a lesser extent, it also competes with traditional transactional databases, these types of as Oracle Database, SQL Server, and IBM DB2, as men and women go their database masses to the cloud and shift their application architectures to microservices.