Tyler Akidau
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Research Interests
Tyler Akidau has a total of 33 co-authors. Here are the top co-authors by number of shared publications:
- Niklas Semmler
Snowflake, Berlin, Germany
3 shared publications - Boyuan Zhang
Snowflake, Bellevue, WA, USA
2 shared publications - Daniel Mills
Snowflake, Bellevue, WA, USA
2 shared publications - Daniel Sotolongo
Snowflake, Bellevue, WA, USA
2 shared publications - Dzmitry Pauliukevich
Snowflake, Berlin, Germany
2 shared publications - Fabian Hueske
Snowflake, Inc., Germany, Berlin
2 shared publications
Latest Publications
- Open Access
- 22 June 2025
- Published by Association for Computing Machinery (ACM)
- p. 622-634
Streaming Democratized: Ease Across the Latency Spectrum with Delayed View Semantics and Snowflake Dynamic Tables
- 22 June 2025
- Published by Association for Computing Machinery (ACM)
- p. 622-634
Open AccessStreaming Democratized: Ease Across the Latency Spectrum with Delayed View Semantics and Snowflake Dynamic Tables
- Open Access
- 24 June 2024
- Published by Association for Computing Machinery (ACM)
- p. 195-198
Continuous Data Ingestion and Transformation in Snowflake
Continuous data growth and the need for close-to-now analytics challenge today's data loading patterns for data warehouses. Traditionally, data is ingested into data warehouses with batch-style loading processes. This also used to be the way to for cloud-based data platforms, such as Snowflake. Data was chunked up into files which were loaded into cloud storage and registered to a table. Subsequently, derived results were fully recomputed if they were based on data sets with new data. Processing inefficiencies and cost concerns prohibited frequent ingestion and refreshes, leaving many latency-sensitive use cases unaddressed. Over the past years, Snowflake has released and improved several features to continuously ingest and transform data. These features ease the definition of declarative data pipelines and enable our users to continuously load huge amounts of data and frequently update derived results in a cost-efficient manner. Snowflake's user interface (UI) provides detailed insights into the operational aspects of data pipelines and supports debugging and failure investigations. With this demo, we show how to seamlessly combine Snowflake's data ingestion and transformation features to built sophisticated data pipelines that cost-efficiently process large amounts of incoming data. Our demo scenario resembles the ingestion and transformation steps of an order analytics system of a B2B retail business. We show and explain the declarative definition of the data pipeline, observe its continuous operation, and leverage Snowflake's UI to dig into details such as query plans for incremental result maintenance.
- 24 June 2024
- Published by Association for Computing Machinery (ACM)
- p. 195-198
Open AccessContinuous Data Ingestion and Transformation in Snowflake
Continuous data growth and the need for close-to-now analytics challenge today's data loading patterns for data warehouses. Traditionally, data is ingested into data warehouses with batch-style loading processes. This also used to be the way to for cloud-based data platforms, such as Snowflake. Data was chunked up into files which were loaded into cloud storage and registered to a table. Subsequently, derived results were fully recomputed if they were based on data sets with new data. Processing inefficiencies and cost concerns prohibited frequent ingestion and refreshes, leaving many latency-sensitive use cases unaddressed. Over the past years, Snowflake has released and improved several features to continuously ingest and transform data. These features ease the definition of declarative data pipelines and enable our users to continuously load huge amounts of data and frequently update derived results in a cost-efficient manner. Snowflake's user interface (UI) provides detailed insights into the operational aspects of data pipelines and supports debugging and failure investigations. With this demo, we show how to seamlessly combine Snowflake's data ingestion and transformation features to built sophisticated data pipelines that cost-efficiently process large amounts of incoming data. Our demo scenario resembles the ingestion and transformation steps of an order analytics system of a B2B retail business. We show and explain the declarative definition of the data pipeline, observe its continuous operation, and leverage Snowflake's UI to dig into details such as query plans for incremental result maintenance.
- Open Access
- 24 June 2024
- Published by Association for Computing Machinery (ACM)
- p. 4-5
Simplicity and Elegance in Stream Processing: a 5-Year Odyssey
- 24 June 2024
- Published by Association for Computing Machinery (ACM)
- p. 4-5
Open AccessSimplicity and Elegance in Stream Processing: a 5-Year Odyssey
- Open Access
- 13 June 2023
- Published by Association for Computing Machinery (ACM) in Proceedings of the ACM on Management of Data
- Vol. 1 (2) , 1-27
What's the Difference? Incremental Processing with Change Queries in Snowflake
Incremental algorithms are the heart and soul of stream processing. Low latency results depend on the ability to react to the subset of changes in a dataset over time rather than reprocessing the entirety of a dataset as it evolves. But while the SQL language is well suited for representing streams of changes (via tables) and their application to tables over time (via DML), it entirely lacks a method to query the changes to a table or view in the first place. In this paper, we present CHANGES queries and STREAM objects, Snowflake's primitives for querying and consuming incremental changes to table objects over time. CHANGES queries and STREAMs have been in use within Snowflake for three years, and see broad adoption across our customers. We describe the semantics of these primitives, discuss the implementation challenges, present an analysis of their usage at Snowflake, and contrast with other offerings.
- 13 June 2023
- Published by Association for Computing Machinery (ACM) in Proceedings of the ACM on Management of Data
- Vol. 1 (2) , 1-27
Open AccessWhat's the Difference? Incremental Processing with Change Queries in Snowflake
Incremental algorithms are the heart and soul of stream processing. Low latency results depend on the ability to react to the subset of changes in a dataset over time rather than reprocessing the entirety of a dataset as it evolves. But while the SQL language is well suited for representing streams of changes (via tables) and their application to tables over time (via DML), it entirely lacks a method to query the changes to a table or view in the first place. In this paper, we present CHANGES queries and STREAM objects, Snowflake's primitives for querying and consuming incremental changes to table objects over time. CHANGES queries and STREAMs have been in use within Snowflake for three years, and see broad adoption across our customers. We describe the semantics of these primitives, discuss the implementation challenges, present an analysis of their usage at Snowflake, and contrast with other offerings.