We are excited to announce the general availability of YugabyteDB 2.2! The highlight of this release is that YugabyteDB now supports fully-transactional distributed backups thus making mission-critical distributed SQL deployments operationally simple, even for the most demanding enterprise environments. This release also includes critical new features such as online index builds, colocated tables, and deferred constraints. The end result is that YugabyteDB continues to make distributed SQL easy. For those of you who are new to distributed SQL, YugabyteDB is a Google Spanner-inspired, cloud native distributed SQL database that is 100% open source. It puts a premium on high performance, data resilience, and geographic distribution while ensuring PostgreSQL wire compatibility.
In this post, we’ll share what’s new in 2.2, and a preview of upcoming features currently in beta.
Summary of New YugabyteDB 2.2 Features
Here’s a summary of the new generally available and beta features in our latest release. All features are described in detail later in this post.
Generally available in release 2.2:
Transactional distributed backups
Online index builds
Deferred constraints for foreign keys
yugabyted server for single-node clusters
Colocated tables
TPC-C results
In beta in release 2.2:
Online schema changes for YCQL
Automatic tablet splitting
yugabyted server for multi-node clusters
Change Data Capture
Also new and noteworthy since our last release:
Design for online schema changes for YSQL
Design for row-level geo-partitioning
Continued community momentum
YugabyteDB 2.2 Generally Available Features in Detail
Transactional Distributed Backups
Prior to this release, YugabyteDB backups came in two flavors: snapshot-based distributed backups that handled single-row transactions and full backups that backed up all committed data of a database. This meant the only way to handle backups with multi-row transactions (even the ones used internally for secondary indexes) was to use full backups. However, full backups are expensive from a resource consumption standpoint and also time intensive for large data sets. The snapshot-based distributed backup approach has now been enhanced to handle multi-row transactions. And this feature is available for both YCQL (in the context of a single table and its associated indexes) as well as YSQL (in the context of all tables and relations in a single SQL database).
#community news #company news #databases #distributed sql #postgresql
