Graettinger: Estuary Flow is not a database and stores no data copies
Johnny Graettinger · Building Real-Time Data Pipelines | Estuary's Johnny Graettinger · Aug 11, 2022 · at 2:22
Johnny Graettinger, Co-Founder and CTO of Estuary, describes the core architecture of Estuary Flow at Data Driven NYC.
0:00 / 0:11exact quote · 11.9s
▶ Watch the full episode on YouTube → 720p mp4 · rendered on demand · StarZero watermark
“But a key thing to understand about Flow is that it is not a database. It is not storing copies of your data. It is really concerned just with coordinating your existing data systems and how data is moving between them.”
quote is from the automated transcript, cleaned for reading: filler sounds and stutters are removed, nothing is rephrased. names can be misheard (the analysis reads context, assessments check outside sources). how →
More from Johnny Graettinger
Graettinger: Estuary charges customers based on compute resource usage
“We're charging on usage, essentially. So we're charging on the actual, like, compute resource that's required in order to get these workflows up and running.”
Graettinger: Estuary Flow processes data incrementally by tracking changes
“Flo's really concerned with just the movement of data through this topology through the data systems that you have, and it's doing it in a very incremental way. So it's looking just at what's changing within any given collection and propagating the effects.”
Estuary's materialization connectors are implemented as Docker container plugins
“Connectors for materializations are essentially Docker container plugins.”