Start Now

Simplify data migration and embrace a cloud native architecture with YugabyteDB Voyager!

Learn More

Category: Amazon Web Services

AWS re:Invent 2018 Recap – The Freedom to Build

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 YugabyteDB is playing its part in shaping that future. This post summarizes our key learnings from the conference, which continues to set the record every year as world’s largest gathering of cloud platform engineers and executives.

Read more

How DynamoDB’s Pricing Works, Gets Expensive Quickly and the Best Alternatives

How DynamoDB’s Pricing Works, Gets Expensive Quickly and the Best Alternatives

DynamoDB is AWS’s NoSQL alternative to Cassandra, primarily marketed to mid-sized and large enterprises. It works best for those who require a flexible data model, reliable performance, and the automatic scaling of throughput capacity. In a nutshell, DynamoDB’s monthly cost is dictated by data storage, writes and reads. Let’s walk through a synopsis.

Read more

Achieving Sub-ms Latencies on Large Datasets in Public Clouds

Achieving Sub-ms Latencies on Large Datasets in Public Clouds

One of our users was interested to learn more about YugabyteDB’s behavior for a random read workload where the data set does not fit in RAM and queries need to read data from disk (i.e. an uncached random read workload).

The intent was to verify if YugabyteDB was designed well to handle this case with the optimal number of IOs to the disk subsystem.

This post is a sneak peak into just one of the aspects of YugabyteDB’s innovative storage engine,

Read more

Practical Tradeoffs in Google Cloud Spanner, Azure Cosmos DB and YugabyteDB

Practical Tradeoffs in Google Cloud Spanner, Azure Cosmos DB and YugabyteDB

Updated April 2019.

The famed CAP Theorem has been a source of much debate among distributed systems engineers. Those of us building distributed databases are often asked how we deal with it. In this post, we dive deeper into the consistency-availability tradeoff imposed by CAP which is only applicable during failure conditions. We also highlight the lesser-known-but-equally-important consistency-latency tradeoff imposed by the PACELC Theorem that extends CAP to normal operations.

Read more

Learn More to Accelerate Your Retail Business

Ready to dive deeper into distributed SQL, YugabyteDB, and Yugabyte Cloud?
Learn at Yugabyte University
Learn More
Browse Yugabyte Docs
Read More
Join the Yugabyte Community
Join Now