Learn how to best use Query Planner hints in the YugabyteDB database to optimize business queries based on how applications expose them. Walk through a use case that utilizes data sets from two popular TV shows to find total viewership per season, episode, etc.
Finding one-to-one mapping of the differences between monolithic and cloud-native databases is difficult.
In this blog, we compare YugabyteDB and Oracle (RAC, Data Guard) via availability objectives.
This should help you understand how Oracle MAA options map to YugabyteDB’s intrinsic features when considering migration projects.
In Java development, garbage collection is a routine task. Applications generate garbage all the time. And that garbage is meticulously cleaned out by CMS, G1, Azul C4 and other types of collectors. Basically, our applications are born to bring value to this world, but nothing is perfect—including our applications that leave litter in the Java heap.
However, the story doesn’t end with the Java heap. In fact, it only starts there. Let’s take the example of a basic Java application that uses a relational database—such as PostgreSQL—and solid state drives (SSDs) as a storage device.
In the first post in this series, we covered how to secure YugabyteDB’s internal RPC protocol using the TLS encryption protocol, also referred to as server-to-server encryption in transit. In this post, we secure the communication between SQL clients and the PostgresQL query interface of YugabyteDB, also called client-to-server encryption in transit.
YugabyteDB—a 100% open source, distributed SQL database built to accelerate cloud native agility—stores important user and customer data at an organization.
ybio is a PL/pgSQL based load generator for PostgreSQL and YSQL. This YugabyteDB-specific IO testing toolkit performs flexible IO testing to specific parts of the YugabyteDB infrastructure with no client installation. And because this toolkit is PL/pgSQL-based, it can also work on native PostgreSQL.
There are many secrets to creating a high-performing database application. One such secret is proper database connection management. However, this secret is not specific to YugabyteDB or PostgreSQL, but applies to any database.
In this post, we examine database connection management through the lens of YugabyteDB. We explore pools and performance, and run tests to measure the results. By the end of this post, you’ll have a clear sense of how to make efficient use of database connection management.
In the second part of this blog series on PostgreSQL and YSQL date-time data types, the focus shifts to representing durations, or how long things last. Assuming the reader has read the first part and downloaded the companion code kit, this post explores the relevant data types, including interval, timestamp difference, and other related functions.
This is the first of a two-part blog post series that deals with the basic business of representing moments using time, date, and timestamp data types. YugabyteDB’s YSQL subsystem provides a similar experience to PostgreSQL, so the topic may still be enlightening for some YSQL users.
PostgreSQL has eaten the world. And so Yugabyte set out to build the most Postgres-compatible, scalable, and resilient database. YugabyteDB is not only wire compatible with PostgreSQL, it is code compatible by reusing the upper half of PostgreSQL. Thanks to this compatibility, YugabyteDB can connect to the vast majority of database tools that integrate with Postgres.
In a previous blog post, Yugabyte Developer Advocate Franck Pachot showed how to connect YugabyteDB in Arctype.
Yugabyte brings best-in-class performance, scalability, and availability to YugabyteDB, a fully PostgreSQL-compatible SQL database. Because YugabyteDB’s architecture uses PostgreSQL at the SQL layer, we get a long-tail of PostgreSQL compatibility for free. But implementing savepoints requires deeper integration into YugabyteDB’s distributed persistence and transaction layers.
In this blog post, we’ll discuss why you should care about savepoints. We’ll also examine how we built savepoints into YugabyteDB’s distributed transaction layer,