Gunnar Morling posted on Twitter: ""Separating storage and compute" vs. "Predicate push-down" -- I can't quite square these two with each other. Is there a world where they co-exist, or is it just two opposing patterns/trends in DB tech. ?"
Those are complimentary patterns and you definitely want them together. They appear contradictory because "separating storage and compute" can mean different things to different people.
In this episode, I explain the various meanings of compute-storage separation, the problems it solves, the new problem it can create, and how predicate pushdown saves the day.
00:00 Welcome
00:22 Gunnar's question
1:12 Coupled storage and compute
1:43 Today's typical architecture
2:15 Did we separate compute and storage yet?
5:21 Elasticity with compute-storage separation
10:13 Using the CPU in storage clusters
12:38 Why predicate pushdown?
15:37 Predicate pushdown as system design pattern
17:22 Better together
My show notes: https://www.thenile.dev/blog/storage-...
Gunnar's tweet: / 1610203324963516417
Aurora paper: https://web.stanford.edu/class/cs245/...