The Distributed SQL Blog

Thoughts on distributed databases, open source and cloud native

YugaByte DB vs CockroachDB Performance Benchmarks for Internet-Scale Transactional Workloads

Enterprises building cloud native services are gravitating towards transactional NoSQL and globally distributed SQL databases as their next-generation transactional stores. There are at least two distinct usage patterns among these cloud native services – internet-scale transactional workloads and scale-out RDBMS workloads. They have a lot of common demands from the database they use, such as transactions/strong consistency,

Read More

Rise of Globally Distributed SQL Databases – Redefining Transactional Stores for Cloud Native Era

At last month’s KubeCon + CloudNativeCon in Seattle, the single biggest change from previous container-related conferences was the excitement among the end user companies around their adoption of Kubernetes and the associated cloud native infrastructure ecosystem. The CNCF End User Community page today lists 50+ enterprises and 21+ case studies including those from industry bellwethers such as Capital One,

Read More

Recapping YugaByte’s 2018 Milestones and a Preview of the 2019 Roadmap

After launching YugaByte DB in November 2017, Team YugaByte celebrated 2018 as its first full year in the market as a cloud native, transactional database company. Exhilarating is the one word that best summarizes our 2018 experience. From a product and engineering standpoint, we launched two major releases (and tens of minor releases) and saw users adopt each of the releases at an amazing pace.

Read More

Why are NoSQL Databases Becoming Transactional?

The NoSQL database revolution started with the publication of the Google BigTable and Amazon Dynamo papers in 2006 and 2007 respectively. These original designs focused on horizontal write scalability without compromising the performance observed in the single node databases dominant at that time. The compromises instead came either in the form of eventual consistency (i.e. inability to read the last update) or loss of multi-key access patterns (such as SQL integrity/foreign key constraints,

Read More

YugaByte Announces Kubernetes StatefulSets Support to Enable Scale-Out PostgreSQL Deployments

YugaByte is excited to be at KubeCon today to announce Kubernetes StatefulSets support for our distributed SQL API which complements the transactional NoSQL APIs already generally available. YSQL is YugaByte DB’s PostgreSQL-compatible Distributed SQL API (currently in Beta). This new feature, available in YugaByte DB 1.1.7, cloud-native applications and microservices can rely on SQL and NoSQL to take full advantage of Kubernetes StatefulSets to power horizontally scalable,

Read More

AWS re:Invent 2018 Recap – The Freedom to Build

Team YugaByte was at AWS re:Invent in Las Vegas last week. While AWS was announcing a flurry of new product releases and existing product updates, we had some excellent deep dive conversations at our booth on the future of transactional databases and how YugaByte DB is playing its part in shaping that future. This post summarizes our key learnings from the conference,

Read More

YugaByte Database Engineering Update – Nov 27, 2018

Lots has happened since our last engineering update about 3 months ago. Below are some of the highlights.

PostgreSQL API Updates & PostgresConf Silicon Valley Wrap-Up

We have made a lot of progress on YSQL, the PostgreSQL compatible distributed SQL API for YugaByte DB! You can also read about YSQL architecture which covers how distributed SQL is implemented in YugaByte DB.

Read More

Data Modeling Basics – PostgreSQL vs. Cassandra vs. MongoDB

Application developers usually spend considerable time evaluating multiple operational databases to find that one database that’s best fit for their workload needs. These needs include simplified data modeling, transactional guarantees, read/write performance, horizontal scaling and fault tolerance. Traditionally, this selection starts out with the SQL vs. NoSQL database categories because each category presents a clear set of trade-offs. High performance in terms of low latency and high throughput is usually treated as a non-compromisable requirement and hence is expected in any database chosen.

Read More