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.
Backend developers working with databases often rely on query builders and object-relational mappings (ORMs) to facilitate database interactions. In this blog, we’ll investigate how the Knex.js query builder can be used to enhance the development experience with Node.js and YugabyteDB.
There is now support for YugabyteDB in Testcontainers. This blog explores how to use Testcontainers to write integration tests for a Spring Boot application with the Yugabyte database.
Developing distributed, database-backed applications brings a number of performance considerations. Applications are being developed to run across zones and regions, potentially incurring high latency costs if incorrectly tuned. This blog will guide you towards a low latency future by using Node.js Smart Drivers.
In this blog, we will explore how to set up the metrics dashboards for YugabyteDB’s CDC operations and how to use them to monitor those operations. We will also explore the behavior of these metrics under various scenarios.
There are many ways to handle ID generation in PostgreSQL. In this blog, we’ll demonstrate four ways to do so in Sequelize for PostgreSQL and YugabyteDB.
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.
This post walks you through how to quickly build an interactive data analytics dashboard in Power BI using the data stored in your YugabyteDB database and specify the storage mode of a table.
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.
To illustrate how to build a geo-distributed application, we will use as an example a Slack-like messaging app. This step-by-step guide starts with the distributed application and API layers, continues on to the distributed SQL database, and finishes with the need/purpose of the global cloud load balancer.