In YugabyteDB, every table and index is sharded across the cluster, with partitioning at the query level (YSQL) and sharding at the storage level (DocDB), enabling unique configuration concepts like row-level geo-partitioning.
In this blog post, we will explore the differences between colocated and non-colocated databases/tables and then dive into the syntax implications of primary key usage on colocated and non-colocated tables/databases.
In this blog post, we explore client connections in YugabyteDB, their impact on scalability, and the role of connection pooling. We address common questions and provide insights for developers looking to design efficient interactions between their applications and the database.
This blog examines the geo-distributed deployment topologies offered with YugabyteDB that can future-proof your data infrastructure and support your app’s needs.
Despite advancements in public clouds, region and zone outages still occur once or twice a year. This blog offers best practices to improve performance and reduce latencies in a multi-region deployment.
This blog post describes the benefits of full compactions, some of the scenarios where they are used, and how to best schedule them in YugabyteDB.
This blog discusses the performance issues with wildcard lookups in YugabyteDB and showcases alternative methods to find specific data in a large dataset, including several varieties of phonetic matching and trigrams. A test plan is provided to demonstrate basic query timings.
Dimitri Farafonov, VP and Fellow Architect at Fiserv, recently sat down to discuss his role at this top global fintech and payments company. During the conversation, he discussed the priorities that guide Fiserv’s database selection process, along with the complexities involved in working to achieve low latency, data consistency, and massive bi-directional scalability, which are critical to Fiserv’s operations.
This blog provides a guide to building Spring Boot applications with YugabyteDB using GraalVM’s ahead-of-time (AOT) compilation to generate a native image. The guide covers the necessary prerequisites and steps to trigger the native build, including how to handle dependencies lacking reachability metadata with explicit runtime hints.
This blog covers the function and implementation compactions, focusing on those details and configurations that are relevant to YugabyteDB. The second half focuses on the behavior and prioritization of background compactions.
