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.
The Distributed SQL Blog
Thoughts on distributed databases, open source, and cloud native
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.
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.
YugabyteDB Managed is a fully managed offering of the YugabyteDB database. It delivers the power of distributed SQL with the ease of use of a database-as-a-service. It’s an effortless distributed SQL database. But what can it help you achieve? This blog walks through four reasons developers and enterprises alike will love YugabyteDB Managed.
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.