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.
YugabyteDB is the first distributed SQL database to receive the designation of AWS Graviton Ready Partner. Learn how we tested and optimized our database using Graviton ARM processors, and see how we delivered strong performance numbers.
Yb_stats is used to obtain YugabyteDB database cluster status for troubleshooting, ad hoc analysis, and support. It gathers all needed facts from every cluster component and stores them in a “snapshot”. Let’s take a look at how this all works.
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.
In this blog post, Solutions Engineer Arisa Izuno shares what attracted her to Yugabyte and to the YugabyteDB database. Spoiler alert: 100% open source, our ability to run everywhere, and the chance to help Japanese companies reach their digital transformation goals.
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.
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.
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.