We aim to prove YugabyteDB’s enhanced Postgres compatibility by migrating 100 popular open source Postgres applications to YugabyteDB! Discover how you can get involved in the Postgres App Century Challenge.
Achieve disaster recovery for cloud-native PostgreSQL deployments using YugabyteDB in Microsoft Azure. Discover how you can leverage YugabyteDB’s xCluster disaster recovery (DR) feature to maintain high availability and ensure data integrity. Use the active-active single-master configuration to achieve disaster recovery across two regions.
Postgres is increasingly being used for Gen AI workloads, but users have reported scalability and performance issues, data privacy challenges and high availability concerns. Before you choose a scalable, HA, vector database instead, try running distributed PostgreSQL. Read our new blog to discover when and how to use distributed PostgreSQL for Gen AI workloads.
Discover why YugabyteDB is moving beyond PostgreSQL 11 and the challenges and solutions involved in upgrading to PostgreSQL 15 (and beyond). Learn how our engineering team is bringing the most popular PostgreSQL features to YugabyteDB, to deliver a reliable, scalable, highly available, and secure distributed SQL database.
The Paramount+ tech team mastered the “art of scaling” by deploying their streaming platform across multiple cloud regions, ensuring high availability and resilience during peak traffic. How can you replicate this scalability and reliability across regions? In this blog, we’ll explore two possible design patterns using a sample application.
Learn to build a scalable AI application with Azure OpenAI Service and YugabyteDB. See how to interface with Azure’s GPT and Embeddings models, embedding storage in YugabyteDB and conducting similarity searches in distributed clusters.
Introducing PgCompute—a client-side extension for PostgreSQL aimed at revitalizing the use of database functions by allowing developers to create and optimize them seamlessly within their preferred IDE and programming language.
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.
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.
