Chris Riccomini's newsletter on databases, stream processing, data infrastructure, and cloud systems, including Kafka, Flink, and incremental view maintenance.
HN commenters praise the posts and cite them in discussions of Kafka's protocol and stream processing history, such as Samza to Flink.
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
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?
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)