Thoughts on distributed databases, open source, and cloud native
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.
So what is a geo-distributed app? It is generally defined as an app that spans multiple geographic locations for high availability and resiliency. However, Iet’s expand (and then break down) that definition for a better understanding.
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.
YugabyteDB for Python (Django) app can achieve high availability (HA) and handle a cloud outage. To demonstrate this, we will simulate an outage in Google Cloud Platform (GCP) on one of the Yugabyte database nodes to see how YugabyteDB handles the downtime.