The Distributed SQL Blog

Thoughts on distributed databases, open source and cloud native

Row Counts of Tables in a SQL Schema & Database – PostgreSQL and YugabyteDB

Getting total row counts of data in tables across various dimensions (per-table, per-schema, and in a given database) is a useful technique to have in one’s tool belt of SQL tricks. While there are a number of use cases for this, my scenario was to get the per-table row counts of all tables in PostgreSQL and YugabyteDB as a first sanity check after migrating an application with the pre-existing data from PostgreSQL to YugabyteDB.

Read More

Using Envoy Proxy’s PostgreSQL & TCP Filters to Collect Yugabyte SQL Statistics

Layer 7 proxies like NGINX and HAProxy have been popular since the mid-2000s. The term “proxy” refers to their role as an intermediary for the traffic between an application client and an application server. The “layer 7” classification comes from the fact that these proxies take routing decisions based on URLs, IPs, TCP/UDP ports, cookies, or any information present in messages sent over a layer 7 (aka application layer) networking protocol like HTTP and gRPC.

Read More

Webinar Recap: CRUD Operations with Hasura GraphQL and Distributed SQL

For those of you who missed last week’s YugabyteDB Community Q&A session, which covered GraphQL fundamentals, here’s the playback:

If you are interested in further exploring the possibilities of Hasura GraphQL and Distributed SQL, check out these resources.

Read More

Getting Started with Hasura GraphQL Remote JOINs on Multi-Cloud Distributed SQL

Remote Joins in Hasura GraphQL extend the concept of joining data across tables, to being able to join data across tables and remote data sources. In this blog post we are going to demonstrate this capability by configuring the following set up.

  • A 3 node YugabyteDB cluster running on GKE with a Hasura GraphQL Engine attached
  • A 3 node YugabyteDB cluster running on AKS with a Hasura GraphQL Engine attached
  • A Remote Schema and Remote Relationship configured
  • The ability to issue GraphQL queries that join data from two different databases,

Read More

Deploying a Real-Time Location App with Hasura GraphQL Engine and Distributed SQL

Hasura is one of the leading vendors in the GraphQL ecosystem. They offer an open source engine that connects to your databases and microservices, and then auto-generates a production-ready GraphQL backend. GraphQL is a query language (more specifically a specification) for your API, and a server-side runtime for executing queries by using a type system you define for your data.

Read More

Run the REST Version of Spring PetClinic with Angular and Distributed SQL on GKE

Java developers know that Spring Data makes it easy to use data access technologies, relational and non-relational databases, map-reduce frameworks, and cloud-based data services. When YugabyteDB is combined with Spring, Java developers are able to leverage their familiarity with PostgreSQL while gaining the added benefits of Distributed SQL. These “out-of-the-box” benefits include geo-data distribution, high performance, and horizontal scalability,

Read More

Staying Connected During COVID-19: Join Us at KubeCon + CloudNativeCon Europe 2020

We are excited to sponsor KubeCon + CloudNativeCon Europe 2020 and participate alongside other open source and cloud native communities coming together to drive cloud native computing forward. Although many people across the world remain physically distanced (us included), we believe that coming together as a community and maintaining a sense of connection are still very essential and important.

Read More

Introducing yugabyted, the Simplest Way to Get Started with YugabyteDB

Users familiar with YugabyteDB’s architecture know that it is based on two servers where cluster metadata storage and administrative operations are managed by a YB-Master metadata server that is independent from the YB-TServer database server. The end result is that the YB-Master server can be configured and tuned (in a manner that is completely isolated from YB-TServer) to achieve higher performance and faster resilience than a single-server architecture.

Read More