At the 5th annual Distributed SQL Summit, Yugabyte CTO, Karthik Ranganathan unveiled product enhancements for YugabyteDB, supercharging PostgreSQL performance and addressing its traditional weak points with innovative features in YugabyteDB 2.19 and Voyager 1.5.
YugabyteDB uses LSM Tree / SST Files to minimize the risk of data corruption, in contrast to PostgreSQL’s method. This approach, coupled with independent compactions and checksum verification, enhances data integrity.
We are excited to share the new Yugabyte logo! Read the launch blog to discover why we decided to update our logo and how the new design reflects the vision, values, and future of Yugabyte!
As 2022 comes to an end, organizations will continue to shift their focus from using monolithic solutions to distributed SQL databases that better align with their cloud native architectures. And that is not the only shakeup we expect to see in the new year!
Check out our top 2023 database predictions based on trends we already see taking shape.
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.
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?
We’re delighted to announce that we have successfully completed our Service Organization Controls (SOC) 2 Type 2 and SOC 3 attestations, covering YugabyteDB, YugabyteDB Anywhere, and YugabyteDB Managed.
Recently, Saul Van Beurden, Head of Technology at Wells Fargo, sat down with Yugabyte CEO Bill Cook to discuss the bank’s modernization, innovation, and digital transformation initiatives. Saul shared his experience, insights, and advice on how any IT leader can drive change—from the technology stack to security, from the importance of building skills to making elephants run, and even a conversation around blueberry muffins!
Every SQL execution in PostgreSQL and therefore in YugabyteDB YSQL takes time to process. A common way to identify how much is time spent on processing is to use the pg_stat_statements view in the database. However, the time visible in pg_stat_statements might differ from the time a database client registers for the execution. Where does this difference come from? Let’s take a look.
As you look to build a streaming application that scales, there are many database options to choose from. If you’re looking for a high-performance database that can handle large-scale data, YugabyteDB,
is a great option. In this blog, we will build an application with YugabyteDB and Django, using the PubNub market order data stream. You will see how you can use YugabyteDB and Django to make an application that subscribes to the PubNub Market Orders Stream, stores these trades in YugabyteDB, and displays them in real-time.