YugabyteDB 2.16 spotlights our continued focus on helping you grow your business with fast, reliable, access to accurate data. Read on to discover the new enhancements released in YugabyteDB 2.16 and the previously announced features now generally available for production deployments.
At Yugabyte, we are continuously working on improving backup and restore capabilities to support various organizational objectives. YugabyteDB 2.17 includes major updates, which we call “Backup 2.0.”
In this blog, we’ll dive into these new updates and show how you can use the added flexibility they provide to lower RPO and RTO.
YugabyteDB 2.17 delivers a number of new xCluster replication enhancements to enable a business continuity/disaster recovery (BCDR) data plan in the event of a cloud region failure. This blog walks through what’s new in YugabyteDB 2.17, and how you can use these enhancements to build an end-to-end BCDR strategy.
We are excited to announce a major wave of product innovations, starting with the availability of YugabyteDB 2.17 and major enhancements to YugabyteDB Managed. Power more business-critical enterprise applications with the industry’s best cloud native database. Read our detailed blog to learn more.
Guy Chiarello, COO at Fiserv, sat down with us to discuss a variety of topics, including innovation in fintech and the entire financial services sector, the trends he’s keeping an eye on, changes he thinks are coming, and why now is the time for another transactional database.
In a previous blog, we developed an application-level sharding layout to avoid hotspots. With that layout in mind, where order is maintained within each shard, let’s discuss how to design a query to return data with pagination while maintaining the global ordering.
YugabyteDB is the first distributed SQL database to receive the designation of AWS Graviton Ready Partner. Learn how we tested and optimized our database using Graviton ARM processors, and see how we delivered strong performance numbers.
Yb_stats is used to obtain YugabyteDB database cluster status for troubleshooting, ad hoc analysis, and support. It gathers all needed facts from every cluster component and stores them in a “snapshot”. Let’s take a look at how this all works.
Some data model choices in distributed databases cause data to grow in one node before it moves to another node. This will cause one node to become a hotspot for reads and writes. This article explains how to avoid that.
Let’s see how to capture pg_stat_statements from all the nodes in a persistent table to use for analysis. The data can then be stored in YugabyteDB tables, accessible from any node unless purged. Want to see how it can be done?