Materialized View
materializedview.io · Personal blog · on HN since 2023
Chris Riccomini's newsletter on databases, stream processing, data infrastructure, and cloud systems, including Kafka, Flink, and incremental view maintenance.
What HN saysHN commenters praise the posts and cite them in discussions of Kafka's protocol and stream processing history, such as Samza to Flink.
21HN people shared it
3linked it in comments
42stories submitted
594story points
4 months agolast shared
2023people per year2026
Most-shared posts
- 1Databases Are Falling Apart: Database Disassembly and Its Implications6 people · 13 points · first shared 2024 · 2 comments on HN
- 2MCP Server Could Have Been a JSON File3 people · 29 points · first shared 2025 · 7 comments on HN
- 3S3 Is the New SFTP, or, how to get data to customers3 people · 11 points · first shared 2024 · discussion on HN
- 4From Samza to Flink: A Decade of Stream Processing3 people · 5 points · first shared 2024 · 1 comments on HN
- 5Everything You Need to Know About Incremental View Maintenance2 people · 10 points · first shared 2025 · 6 comments on HN
- 6Virtual Machines Are Getting Better2 people · 5 points · first shared 2024 · discussion on HN
- 7AI IDEs Need Moats2 people · 3 points · first shared 2025 · discussion on HN
- 8The New Era of Flexible Infrastructure Deployment2 people · 3 points · first shared 2024 · discussion on HN
- 9Ce n'est pas un Kafka: Kafka is a Protocol2 people · 2 points · first shared 2024 · discussion on HN
- 10Nimble and Lance: The Parquet Killers2 people · 1 points · first shared 2024 · discussion on HN
- 11S3 is showing its age1 people · 260 points · first shared 2024 · 166 comments on HN
- 12Database Isolation Is Broken and You Should Care1 people · 121 points · first shared 2023 · 52 comments on HN
- 13Modular Monoliths Are a Good Idea1 people · 101 points · first shared 2024 · 69 comments on HN
- 14How Fast Can Java Parse 1B Rows of Temperature Data1 people · 5 points · first shared 2024 · discussion on HN
- 15PostgreSQL Extensions or Protocols: Architecture Roulette1 people · 4 points · first shared 2024 · discussion on HN
What HN people wrote when they linked it
jauntywundrkind · 2024-02-12
Been loving your posts Chris! The suggestion here sounds awesome. I'd love a little more in depth example of what might go across the wire- the one example was probably more than enough for many but I was still curious technically what these query plans structurally looked like.
Kind of interesting in light of the previous submission, which I truly loved, on the diassbly of the data stack. Great post, and about decentralization of the technology. Yet this post is about a shared tie that could/should help bind, as so many different things are happening. https://materializedview.io/p/databases-are-falling-apart
62951413 · 2024-08-27
Ce n'est pas un Kafka: Kafka is a Protocol Apache Kafka is an aging open source project. It's time to accept that Kafka's protocol is what matters. (https://materializedview.io/p/ce-nest-pas-un-kafka)
amath · 2024-03-18
Nice work on the performance boost :).
How does it compare with things like: 1. https://github.com/bytewax/bytewax 2. https://github.com/pathwaycom/pathway
I recently read this article (https://materializedview.io/p/from-samza-to-flink-a-decade-of-stream) about Flink and it commented on Flink grew to fit all of these different use cases (applications, analytics and ETL) with disjoint requirements that Confluent built kafka-streams, ksql and connector for. What of those would you say Arroyo is better suited for?