In this blog, we explore how to transfer and process data from YugabyteDB (YBDB) to Azure Blob Storage or Azure Data Lake Storage using Azure EventHub through YBDB’s Change Data Capture (CDC) feature.
Our team continues to deliver new innovations, so we are excited to announce our latest stable release—YugabyteDB 2.14, which delivers higher performance, security and YugabyteDB Anywhere enhancements.
YugabyteDB is quickly becoming the cloud native relational database for the world’s most demanding enterprises, driving data-driven innovation in the face of growth, uncertainty, and change.
This blog post explores the most popular multi-region database deployment options by designing a data layer for a Slack-like corporate messenger.
If you are designing your architecture for stateful edge applications, here are some key principles and design patterns you should be aware of.
Hello. I’m Sahith, a Yugabyte engineering intern. I’m a 2022 Computer Science Engineer graduate from PES University in Bangalore who loves to solve problems with code. I also recently decided to join Yugabyte in a full-time engineering role. And lucky for me, this turned out to be one of the best decisions I’ve made.
However, before joining the company full time, I wanted to share some takeaways from my internship experience.
We’ll use YugabyteDB’s CDC SDK server, an open source project that provides a streaming platform for CDC. We’ll also use Snowpipe to automate data loading to files as soon as they are available in a S3 bucket.
Before you begin
Before getting started,
The following text is an excerpt from the new white paper, Migrating From Monolithic to Cloud Native Operational Databases
In this section, we walk through the three challenges of using current generation NoSQL databases: operational complexity, frustrating application development, and inconsistent customer experiences.
1. NoSQL operational complexity
As noted in the previous section, databases have evolved to become cloud hosted but are far from cloud native.