Get startedSign in
Main
Product
Solutions
Build Securely by DefaultAccelerate Your Path To ComplianceLower Cost & ComplexityAccelerate Kubernetes Adoption
Info
PricingDocsMarketplace
Company
AboutBlogCareersContactCommunity
Plural Menu
Get startedSign in
Back

Yugabyte

High-performance NewSQL database for cloud-native applications.

Available providers

Why use Yugabyte on Plural?

Plural helps you deploy and manage the lifecycle of open-source applications on Kubernetes. Our platform combines the scalability and observability benefits of managed SaaS with the data security, governance, and compliance benefits of self-hosting Yugabyte.

If you need more than just Yugabyte, look for other cloud-native and open-source tools in our marketplace of curated applications to leapfrog complex deployments and get started quickly.

Yugabyte’s websiteGitHubLicenseInstalling Yugabyte docs
Deploying Yugabyte is a matter of executing these 3 commands:
plural bundle install yugabyte yugabyte-aws
plural build
plural deploy --commit "deploying yugabyte"
Read the install documentation
YugabyteDB

License Documentation Status Ask in forum Slack chat Analytics

What is YugabyteDB?

YugabyteDB is a high-performance, cloud-native, distributed SQL database that aims to support all PostgreSQL features. It is best suited for cloud-native OLTP (i.e., real-time, business-critical) applications that need absolute data correctness and require at least one of the following: scalability, high tolerance to failures, or globally-distributed deployments.

Core Features

  • Powerful RDBMS capabilities Yugabyte SQL (YSQL for short) reuses the query layer of PostgreSQL (similar to Amazon Aurora PostgreSQL), thereby supporting most of its features (datatypes, queries, expressions, operators and functions, stored procedures, triggers, extensions, etc). Here is a detailed list of features currently supported by YSQL.

  • Distributed transactions The transaction design is based on the Google Spanner architecture. Strong consistency of writes is achieved by using Raft consensus for replication and cluster-wide distributed ACID transactions using hybrid logical clocks. Snapshot, serializable and read committed isolation levels are supported. Reads (queries) have strong consistency by default, but can be tuned dynamically to read from followers and read-replicas.

  • Continuous availability YugabyteDB is extremely resilient to common outages with native failover and repair. YugabyteDB can be configured to tolerate disk, node, zone, region, and cloud failures automatically. For a typical deployment where a YugabyteDB cluster is deployed in one region across multiple zones on a public cloud, the RPO is 0 (meaning no data is lost on failure) and the RTO is 3 seconds (meaning the data being served by the failed node is available in 3 seconds).

  • Horizontal scalability Scaling a YugabyteDB cluster to achieve more IOPS or data storage is as simple as adding nodes to the cluster.

  • Geo-distributed, multi-cloud YugabyteDB can be deployed in public clouds and natively inside Kubernetes. It supports deployments that span three or more fault domains, such as multi-zone, multi-region, and multi-cloud deployments. It also supports xCluster asynchronous replication with unidirectional master-slave and bidirectional multi-master configurations that can be leveraged in two-region deployments. To serve (stale) data with low latencies, read replicas are also a supported feature.

  • Multi API design The query layer of YugabyteDB is built to be extensible. Currently, YugabyteDB supports two distributed SQL APIs: Yugabyte SQL (YSQL), a fully relational API that re-uses query layer of PostgreSQL, and Yugabyte Cloud QL (YCQL), a semi-relational SQL-like API with documents/indexing support with Apache Cassandra QL roots.

  • 100% open source YugabyteDB is fully open-source under the Apache 2.0 license. The open-source version has powerful enterprise features such as distributed backups, encryption of data-at-rest, in-flight TLS encryption, change data capture, read replicas, and more.

Read more about YugabyteDB in our FAQ.

Get Started

Cannot find what you are looking for? Have a question? Please post your questions or comments on our Community Slack or Forum.

Build Apps

YugabyteDB supports many languages and client drivers, including Java, Go, NodeJS, Python, and more. For a complete list, including examples, see Drivers and ORMs.

What's being worked on?

This section was last updated in May, 2023.

Current roadmap

Here is a list of some of the key features being worked on for the upcoming releases (the YugabyteDB v2.17 preview release has been released in Jan, 2023, and the v2.16 stable release was released in Jan 2023).

| Feature | Status | Release Target | Progress | Comments | | ----------------------------------------------- | --------- | -------------- | --------------- | ------------- | | Automatic tablet splitting enabled by default | PROGRESS | v2.18 | Track |Enables changing the number of tablets (which are splits of data) at runtime.| |Upgrade to PostgreSQL v15| PROGRESS| v2.21 |Track| For latest features, new PostgreSQL extensions, performance, and community fixes |Database live migration using YugabyteDB Voyager| PROGRESS| | Track|Database live migration using YugabyteDB Voyager| | Support wait-on-conflict concurrency control | PROGRESS | v2.19 | Track | Support wait-on-conflict concurrency control | | Support for transactions in async xCluster replication | PROGRESS | v2.19 | Track | Apply transactions atomically on target cluster. | | YSQL-table statistics and cost based optimizer(CBO) | PROGRESS | v2.21 | Track | Improve YSQL query performance | | YSQL-Feature support - ALTER TABLE | PROGRESS | v2.21 | Track | Support for various ALTER TABLE variants | | Support for GiST indexes | PLANNING | | Track |Support for GiST (Generalized Search Tree) based index| | Connection Management | PROGRESS | | Track |Server side connection management|

Recently released features

| Feature | Status | Release Target | Docs / Enhancements | Comments | | ----------------------------------------------- | --------- | -------------- | ------------------- | ------------- | |Faster Bulk-Data Loading in YugabyteDB| ✅ DONE| v2.15 |Track| Faster Bulk-Data Loading in YugabyteDB| |Change Data Capture| ✅ DONE| v2.13 ||Change data capture (CDC) allows multiple downstream apps and services to consume the continuous and never-ending stream(s) of changes to Yugabyte databases| |Support for materalized views | ✅ DONE| v2.13 |Docs|A materialized view is a pre-computed data set derived from a query specification and stored for later use| |Geo-partitioning support for the transaction status table | ✅ DONE| v2.13 |Docs|Instead of central remote transaction execution metatda, it is now optimized for access from different regions. Since the transaction metadata is also geo partitioned, it eliminates the need for round-trip to remote regions to update transaction statuses.| | Transparently restart transactions | ✅ DONE| v2.13 | |Decrease the incidence of transaction restart errors seen in various scenarios | | Row-level geo-partitioning | ✅ DONE| v2.13 |Docs|Row-level geo-partitioning allows fine-grained control over pinning data in a user table (at a per-row level) to geographic locations, thereby allowing the data residency to be managed at the table-row level.| | YSQL-Support GIN indexes | ✅ DONE | v2.11 | Docs | Support for generalized inverted indexes for container data types like jsonb, tsvector, and array | | YSQL-Collation Support | ✅ DONE | v2.11 |Docs |Allows specifying the sort order and character classification behavior of data per-column, or even per-operation according to language and country-specific rules | YSQL-Savepoint Support | ✅ DONE | v2.11 |Docs | Useful for implementing complex error recovery in multi-statement transaction| | xCluster replication management through Platform | ✅ DONE | v2.11 | Docs |
| Spring Data YugabyteDB module | ✅ DONE | v2.9 | Track | Bridges the gap for learning the distributed SQL concepts with familiarity and ease of Spring Data APIs | | Support Liquibase, Flyway, ORM schema migrations | ✅ DONE | v2.9 | Docs | | Support ALTER TABLE add primary key | ✅ DONE | v2.9 | Track | | | YCQL-LDAP Support | ✅ DONE | v2.8 |Docs | support LDAP authentication in YCQL API |
| Platform Alerting and Notification | ✅ DONE | v2.8 | Docs | To get notified in real time about database alerts, user defined alert policies notify you when a performance metric rises above or falls below a threshold you set.|
| Platform API | ✅ DONE | v2.8 | Docs | Securely Deploy YugabyteDB Clusters Using Infrastructure-as-Code|

Architecture

YugabyteDB Architecture

Review detailed architecture in our Docs.

Need Help?

Contribute

As an open-source project with a strong focus on the user community, we welcome contributions as GitHub pull requests. See our Contributor Guides to get going. Discussions and RFCs for features happen on the design discussions section of our Forum.

License

Source code in this repository is variously licensed under the Apache License 2.0 and the Polyform Free Trial License 1.0.0. A copy of each license can be found in the licenses directory.

The build produces two sets of binaries:

  • The entire database with all its features (including the enterprise ones) are licensed under the Apache License 2.0
  • The binaries that contain -managed in the artifact and help run a managed service are licensed under the Polyform Free Trial License 1.0.0.

By default, the build options generate only the Apache License 2.0 binaries.

Read More

How Plural works

We make it easy to securely deploy and manage open-source applications in your cloud.

Select from 90+ open-source applications

Get any stack you want running in minutes, and never think about upgrades again.

Securely deployed on your cloud with your git

You control everything. No need to share your cloud account, keys, or data.

Designed to be fully customizable

Built on Kubernetes and using standard infrastructure as code with Terraform and Helm.

Maintain & Scale with Plural Console

Interactive runbooks, dashboards, and Kubernetes api visualizers give an easy-to-use toolset to manage application operations.

Learn more
Screenshot of app installation in Plural app

Build your custom stack with Plural

Build your custom stack with over 90+ apps in the Plural Marketplace.

thing
Airbyte
DATA
Clickhouse
DATA
Dagster
DATA
Datahub
DATA
Growthbook
DATA
Jitsu
DATA
Lightdash
DATA
Posthog
DATA
Explore the Marketplace

Used by fast-moving teams at

  • CoachHub
  • Digitas
  • Fnatic
  • FSN Capital
  • Justos
  • Mott Mac

What companies are saying about us

We no longer needed a dedicated DevOps team; instead, we actively participated in the industrialization and deployment of our applications through Plural. Additionally, it allowed us to quickly gain proficiency in Terraform and Helm.

Walid El Bouchikhi
Data Engineer at Beamy

I have neither the patience nor the talent for DevOps/SysAdmin work, and yet I've deployed four enterprise-caliber open-source apps on Kubernetes... since 9am today. Bonkers.

Sawyer Waugh
Head of Engineering at Justifi

This is awesome. You saved me hours of further DevOps work for our v1 release. Just to say, I really love Plural.

Ismael Goulani
CTO & Data Engineer at Modeo

Wow! First of all I want to say thank you for creating Plural! It solves a lot of problems coming from a non-DevOps background. You guys are amazing!

Joey Taleño
Head of Data at Poplar Homes

We have been using Plural for complex Kubernetes deployments of Kubeflow and are excited with the possibilities it provides in making our workflows simpler and more efficient.

Jürgen Stary
Engineering Manager @ Alexander Thamm

Plural has been awesome, it’s super fast and intuitive to get going and there is zero-to-no overhead of the app management.

Richard Freling
CTO and Co-Founder at Commandbar

Case Study – How Fnatic Deploys Their Data Stack with Plural

Fnatic is a leading global esports performance brand headquartered in London, focused on leveling up gamers. At the core of Fnatic’s success is its best-in-class data team. The Fnatic data team relies on third-party applications to serve different business functions with every member of the organization utilizing data daily. While having access to an abundance of data is great, it opens up a degree of complexity when it comes to answering critical business questions and in-game analytics for gaming members.

To answer these questions, the data team began constructing a data stack to solve these use cases. Since the team at Fnatic are big fans of open-source they elected to build their stack with popular open-source technologies.

Read full study

Fnatic’s Data Stack

Airbyte
Airflow
Clickhouse
Grafana
Metabase
PostgreSQL

FAQ

Plural is open-source and self-hosted. You retain full control over your deployments in your cloud. We perform automated testing and upgrades and provide out-of-the-box Day 2 operational workflows. Monitor, manage, and scale your configuration with ease to meet changing demands of your business. Read more.

We support deploying on all major cloud providers, including AWS, Azure, and GCP. We also support all on-prem Kubernetes clusters, including OpenShift, Tanzu, Rancher, and others.

No, Plural does not have access to any cloud environments when deployed through the CLI. We generate deployment manifests in the Plural Git repository and then use your configured cloud provider's CLI on your behalf. We cannot perform anything outside of deploying and managing the manifests that are created in your Plural Git repository. However, Plural does have access to your cloud credentials when deployed through the Cloud Shell. Read more.