Summary
Stream processing systems have long been built with a code-first design, adding SQL as a layer on top of the existing framework. RisingWave is a database engine that was created specifically for stream processing, with S3 as the storage layer. In this episode Yingjun Wu explains how it is architected to power analytical workflows on continuous data flows, and the challenges of making it responsive and scalable.
Announcements
Hello and welcome to the Data Engineering Podcast, the show about modern data management
Data lakes are notoriously complex. For data engineers who battle to build and scale high quality data workflows on the data lake, Starburst powers petabyte-scale SQL analytics fast, at a fraction of the cost of traditional methods, so that you can meet all your data needs ranging from AI to data applications to complete analytics. Trusted by teams of all sizes, including Comcast and Doordash, Starburst is a data lake analytics platform that delivers the adaptability and flexibility a lakehouse ecosystem promises. And Starburst does all of this on an open architecture with first-class support for Apache Iceberg, Delta Lake and Hudi, so you always maintain ownership of your data. Want to see Starburst in action? Go to dataengineeringpodcast.com/starburst and get $500 in credits to try Starburst Galaxy today, the easiest and fastest way to get started using Trino.
Dagster offers a new approach to building and running data platforms and data pipelines. It is an open-source, cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability, a declarative programming model, and best-in-class testability. Your team can get up and running in minutes thanks to Dagster Cloud, an enterprise-class hosted solution that offers serverless and hybrid deployments, enhanced security, and on-demand ephemeral test deployments. Go to dataengineeringpodcast.com/dagster today to get started. Your first 30 days are free!
Your host is Tobias Macey and today I'm interviewing Yingjun Wu about the RisingWave database and the intricacies of building a stream processing engine on S3
Interview
Introduction
How did you get involved in the area of data management?
Can you describe what RisingWave is and the story behind it?
There are numerous stream processing engines, near-real-time database engines, streaming SQL systems, etc. What is the specific niche that RisingWave addresses?
What are some of the platforms/architectures that teams are replacing with RisingWave?
What are some of the unique capabilities/use cases that RisingWave provides over other offerings in the current ecosystem?
Can you describe how RisingWave is architected and implemented?
How have the design and goals/scope changed since you first started working on it?
What are the core design philosophies that you rely on to prioritize the ongoing development of the project?
What are the most complex engineering challenges that you have had to address in the creation of RisingWave?
Can you describe a typical workflow for teams that are building on top of RisingWave?
What are the user/developer experience elements that you have prioritized most highly?
What are the situations where RisingWave can/should be a system of record vs. a point-in-time view of data in transit, with a data warehouse/lakehouse as the longitudinal storage and query engine?
What are the most interesting, innovative, or unexpected ways that you have seen RisingWave used?
What are the most interesting, unexpected, or challenging lessons that you have learned while working on RisingWave?
When is RisingWave the wrong choice?
What do you have planned for the future of RisingWave?
Contact Info
yingjunwu on GitHub
Personal Website
LinkedIn
Parting Question
From your perspective, what is the biggest gap in the tooling or technology for data management today?
Closing Announcements
Thank you for listening! Don't forget to check out our other shows.
