explaingit

yugabyte/yugabyte-db

10,275CAudience · ops devopsComplexity · 5/5LicenseSetup · hard

TLDR

A distributed database that looks and behaves like PostgreSQL but runs across multiple servers or cloud regions automatically, keeping your data safe and your app online even when servers fail.

Mindmap

mindmap
  root((YugabyteDB))
    What it does
      Distributed PostgreSQL
      Multi-node database
    Key features
      PostgreSQL compatible
      Automatic failover
      Horizontal scaling
      Multi-region support
    Deployment
      Kubernetes
      Single or multi-cloud
      Managed cloud service
    Integrations
      Java drivers
      Go drivers
      Python and Node.js
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Scale a PostgreSQL-backed application beyond a single server by migrating to YugabyteDB without rewriting SQL queries

USE CASE 2

Run a database cluster that keeps serving traffic automatically when one or more nodes go offline

USE CASE 3

Deploy a database that spans multiple cloud regions so users worldwide get fast local reads

USE CASE 4

Add nodes to a live cluster to handle more traffic or store more data without restarting or reconfiguring anything

Tech stack

CPostgreSQLKubernetesJavaGoPythonNode.js

Getting it running

Difficulty · hard Time to first run · 1day+

Requires provisioning multiple server nodes or a Kubernetes cluster, single-node local testing is possible but production setup involves significant infrastructure planning.

Use, modify, and distribute freely for any purpose, including commercial use, as long as you include the Apache 2.0 license notice.

In plain English

YugabyteDB is a database system designed for applications that need to store and query large amounts of data reliably across multiple servers or multiple cloud regions at once. Unlike a traditional database that runs on a single machine, YugabyteDB splits its data across many machines automatically, so it can keep working even if some of those machines fail. It is aimed at business-critical applications where losing data or going offline is not acceptable. The database speaks the same language as PostgreSQL, which is one of the most popular open-source database systems in the world. That means software written to work with PostgreSQL can generally talk to YugabyteDB without changes, including support for the same data types, queries, stored procedures, and many popular extensions. This compatibility is one of the main reasons teams choose it when they need to scale a PostgreSQL-backed application beyond what a single server can handle. YugabyteDB guarantees that transactions are processed correctly even when data is spread across many nodes. If a node goes offline, the system automatically recovers within a few seconds and no data is lost, according to the project's documentation. Operators can add more nodes to the cluster to handle more traffic or store more data without restarting anything. The system can run on a single cloud provider or across multiple cloud providers at the same time, and it supports Kubernetes, a popular tool for managing containerized applications. It also supports read replicas, which are copies of the data placed in other geographic regions to serve users with lower delays. YugabyteDB is open-source under the Apache 2.0 license. The company behind it also offers a managed cloud service. Drivers and integration examples are available for Java, Go, Node.js, Python, and other languages.

Copy-paste prompts

Prompt 1
How do I migrate my existing PostgreSQL app to YugabyteDB and what SQL features or extensions might not work the same way?
Prompt 2
Walk me through setting up a 3-node YugabyteDB cluster on Kubernetes and connecting a Node.js app to it
Prompt 3
How does YugabyteDB handle a node failure mid-transaction and how long does automatic recovery take?
Prompt 4
How do I set up read replicas in YugabyteDB across two AWS regions to reduce read latency for users in Europe?
Open on GitHub → Explain another repo

← yugabyte on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.