Why Materialize: Recommended Reading List
Published: 2021-10-07 15:38:00

---
title: "Why Materialize: Recommended Reading List"
description: A collection of articles that convinced me about the necessity and long-term inevitability of a technology like Materialize.
cover_image: https://andyhattemer.com/posts/why-materialize-reading-list/bridge_over_stream.jpg
published: true
---


This is a growing collection of articles, podcasts, and other media that convinced me that:

1. Technology that incrementally maintains materialized views of data is difficult, but necessary and inevitable
2. [Materialize](https://materialize.com/) is the best shot at making that available to a wide array of developers.

These are probably most relevant to people with operational experience in the data space. You don't need to be technical but it's useful if you've rolled up your sleeves and dug into some of the complicated bits of working with data at scale. They don't need to be read in a particular order.

* Listen to Materialize cofounder Arjun Narayan's podcast on the Data Stack Show: [A New Paradigm in Stream Processing](https://datastackshow.com/podcast/46-a-new-paradigm-in-stream-processing-with-arjun-narayan-of-materialize/)

* Watch our other cofounder and chief scientist [Frank McSherry's DataCouncil talk on Materialize](https://www.youtube.com/watch?v=zWSdkGq1XWk) to get a feel for how Materialize works.

* Read Jon Gjengset’s “simple english” explanation of batch vs incremental [https://jon.thesquareplanet.com/noria-in-simpler-terms.pdf](https://jon.thesquareplanet.com/noria-in-simpler-terms.pdf) - _This is just a really great non-technical way of explaining the traditional database vs incrementally-maintained db with a fun metaphor. This guy is a legend in the space who created his own approach to incremental view maintenance as an MIT thesis, but has since moved on to other things._

* Read Nikita Tonsky’s “[Web After Tomorrow](https://tonsky.me/blog/the-web-after-tomorrow/)” - _Another legend, he is thinking about things from an application developer’s perspective, looking for a “reactive database” but it is eye-opening. Be warned that we are still a ways away from developing a product that is good enough to just quickly slot in and solve this problem._

* Read [Data Denormalization is Broken](https://lironshapira.medium.com/data-denormalization-is-broken-7b697352f405) - _This is a good practical explainer of why something like Materialize should exist._

* Read [A Data Pipeline is a Materialized View](https://nchammas.com/writing/data-pipeline-materialized-view) - _If the one above is for application development, this post lays out the case for Materialized Views for data engineering._

* Read Tristan Handy’s [post/rant about the limits of incrementally updated tabl](https://discourse.getdbt.com/t/on-the-limits-of-incrementality/)es in data warehouses. - _This is more of an answer to "Why NOT just work with the paradigms we have."_

Once you're finished, if you're excited about Materialize, [check out our jobs page](https://grnh.se/acc51dec4us), if you're interested in building on-ramps to Materialize by contributing both writing and code, read about [our developer experience team](https://andyhattemer.com/posts/developer-experience-at-materialize/) and reach out if it interests you!