In a distributed database, data is split into multiple tablets which reside on different nodes. So it is not just tables, but indexes, that are distributed across nodes. So let’s examine how to optimally design distributed indexes to get the best query performance.
Jay Duraisamy, the SVP of Technology for Data and Analytics at Fiserv, sat down with us to discuss how Fiserv is unlocking the value of their data and providing new services for both merchants and consumers by bringing together data and analytics on one platform.
In this blog post, we will explore the primary key 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.
Tom Eck, Sr. Vice President of Digital Transformation at Fiserv, sat down with us to discuss all things application development, including how Fiserv is planning to monetize their data and how application development teams need to modernize to best support cloud native applications.
In this excerpt from the recent white paper, Migrating From Monolithic to Cloud Native Operational Databases, we look at three of the challenges faced by companies using the current generation of NoSQL databases and why distributed SQL may be a better choice.
Lokesh Duseja, Director of Digital Engineering and Architecture at Bed Bath and Beyond sat down with us to chat about their database modernization journey. Topics covered included why distributed SQL made sense, how they evaluated various vendors and tested YugabyteDB, and some of the big “aha” moments they had during this process.
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.
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.
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.
It’s a common misconception that NewSQL and distributed SQL databases are the same. They’re not. Even though they’re both an evolution in the transactional database, there are significant differences. Distributed SQL adoption is growing because companies face new challenges that cannot be easily addressed with NoSQL, SQL, or NewSQL databases. Let’s look at five of them.