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.
In an earlier blog, we broke down the definition of geo-distributed apps. So now let’s compare and contrast geo-distributed apps those apps that are deployed within a single data center or availability zone. A good way to make this comparison to understand the differences and find the similarities is to drill down into the architecture.
As we scale Yugabyte for growth, we know that our entire company needs to be firmly anchored to a strong set of principles. These principles should act as a guiding light for every decision we make and should also define our company culture. After many discussions and analysis, a core theme appeared—transparency.
DSS 2022 was the biggest and best distributed SQL event to date, with so many people engaged and enthused by distributed SQL and YugabyteDB. There were over 25 world-class keynotes, insightful fireside chats with industry-leading enterprises, and technical presentations by YugabyteDB and industry experts.
In case you missed the event or have not yet watched the replays, here are our top five takeaways!
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.
…
Change Data Capture (CDC) is a technique to capture changes in a source database system in real-time. The goal is to stream those changes as events through a data processing pipeline for further processing.
CDC enables many use cases, especially in modern microservices-based architecture that involves a lot of bounded services. It is the de-facto choice for use cases such as search indexes, in-memory data cache, real-time notifications, data sync between sources,
…
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.
At a recent Distributed SQL Summit, Sriram Samu, VP of Customer Technology at Kroger, discussed how his company’s data architecture unlocks digital and omnichannel experiences at scale. He provided a rare glimpse into how the business is bringing its data models into a new format. This format is easy to serve at speed, while still being able to integrate with legacy systems.