The Distributed SQL Blog

Cloud Native Meets Distributed SQL: Bringing Microservices, Kubernetes, Istio & YugabyteDB Together with Hipster Shop Demo

Cloud Native Meets Distributed SQL: Bringing Microservices, Kubernetes, Istio & YugabyteDB Together with Hipster Shop Demo

Polyglot persistence is the widely accepted database implementation strategy when it comes to decomposing monoliths into microservices. In practice, this requires every microservice to model its data needs independently using a database that is purpose-built for that particular model, and thereafter store the data in an independent database instance. While independent database instances as a deployment paradigm makes sense from an decoupled microservices architecture standpoint, choosing multiple different databases each with a specialized data model is usually justified in the context of performance,

Read more

5 Query Pushdowns for Distributed SQL and How They Differ from a Traditional RDBMS

5 Query Pushdowns for Distributed SQL and How They Differ from a Traditional RDBMS

A pushdown is an optimization to improve the performance of a SQL query by moving its processing as close to the data as possible. Pushdowns can drastically reduce SQL statement processing time by filtering data before transferring it over the network, filtering data before loading it into memory, or pruning out entire files or blocks that  do not need to be read. PostgreSQL is a highly optimized single-node RDBMS when it comes to pushdowns. Because Yugabyte’s YSQL API reuses the upper half of PostgreSQL,

Read more

YugabyteDB Engineering Update – Feb 28, 2020

YugabyteDB Engineering Update – Feb 28, 2020

We are excited to announce that YugabyteDB 2.1 went GA earlier this week! You can read the official release notes here. This release shipped with almost 70 new enhancements and fixes.

What’s YugabyteDB? It is an open source, high-performance distributed SQL database built on a scalable and fault-tolerant design inspired by Google Spanner. Yugabyte’s SQL API (YSQL) is PostgreSQL wire compatible.

Highlights of this release include:

Generally Available Features

Geo-distributed,

Read more

Getting Started with Distributed SQL on YugabyteDB Managed

Getting Started with Distributed SQL on YugabyteDB Managed

With the release of YugabyteDB 2.1 earlier this week, we introduced many exciting new features: performance optimizations, 2DC and read replica support, and more. We also announced that YugabyteDB Managed (formerly Yugabyte Cloud) is now officially in Beta! In this blog post we’ll show you how to quickly get up and running with a YugabyteDB cluster on YugabyteDB Managed, build a sample database, and connect to it with JetBrain’s DataGrip database administration tool.

Read more

YugabyteDB 2.1 is GA: Scaling New Heights with Distributed SQL

YugabyteDB 2.1 is GA: Scaling New Heights with Distributed SQL

Team Yugabyte is excited to announce the general availability of YugabyteDB 2.1! The highlight of this release is that Yugabyte SQL (YSQL), YugabyteDB’s PostgreSQL-compatible API, has not only improved performance 10x since the 2.0 release in September 2019 but is also production ready for multiple geo-distributed deployment scenarios. For those of you who are new to distributed SQL, YugabyteDB is a Google Spanner-inspired, cloud native distributed SQL database that is 100% open source.

Read more

Achieving 10x Better Distributed SQL Performance in YugabyteDB 2.1

Achieving 10x Better Distributed SQL Performance in YugabyteDB 2.1

When starting the YugabyteDB project, our founding thesis was to build a high-performance distributed SQL database for the cloud native era. Achieving high performance will always remain an ongoing initiative, especially when additional optimizations are required to support new features and new use cases. We are excited that the current YugabyteDB 2.1 release has a number of improvements that make Yugabyte SQL’s performance 10x better on average than the previous 2.0 release (from September 2019).

Read more

Getting Started with JetBrains DataGrip on a Distributed SQL Database

Getting Started with JetBrains DataGrip on a Distributed SQL Database

If you’re a database developer, you know the time saving value of an IDE in helping you create and navigate database objects, plus query and edit data from single UI. DataGrip from JetBrains is a well-rounded, visual database tool that supports almost 20 SQL and NoSQL databases from a single interface. And because YugabyteDB is PostgreSQL compatible, getting DataGrip to work with a distributed SQL database is relatively simple. In this post we’ll show you how to get DataGrip connected to a YugabyteDB cluster,

Read more

Distributed SQL Tips and Tricks – Feb 21, 2020

Distributed SQL Tips and Tricks – Feb 21, 2020

Welcome to this week’s tips and tricks blog where we recap some distributed SQL questions from around the Internet. We’ll also review upcoming events, new documentation, and blogs that have been published since the last post. Got questions? Make sure to ask them on our YugabyteDB Slack channel, Forum, GitHub, or Stackoverflow. Ok, let’s dive right in:

When should I use JSON vs JSONB data types?

Read more

Developing Reactive Microservices with Spring Data and Distributed SQL

Developing Reactive Microservices with Spring Data and Distributed SQL

In 2016 in the keynote presentation of Spring One Platform, Juergen Hoeller announced Spring WebFlux, one of the most highly anticipated projects being worked on by the Spring Team due to the performance gains that reactive streams promised for web controllers. Subsequently, with Spring Framework 5.0, Spring Reactive MVC went GA along with the release of WebFlux API, making the reactive stream based web controller mainstream.

Fast-forward to 2020, Spring WebFlux MVC has gained wide adoption in cloud native applications,

Read more

Natural versus Surrogate Primary Keys in a Distributed SQL Database

Natural versus Surrogate Primary Keys in a Distributed SQL Database

There’s a subtle, but critical, difference between the two notions business-unique key and primary key in a relational database. For example, in a users” table, the “user_id” could be the primary key while the “email_address” (which must be not null and unique) could be the business-unique key. The columns that implement each notion may or may not coincide. This post shows that,

Read more

Explore Distributed SQL and YugabyteDB in Depth

Discover the future of data management.
Learn at Yugabyte University
Get Started
Browse Yugabyte Docs
Explore docs
PostgreSQL For Cloud Native World
Read for Free