Explore >> Select a destination
|
You are here 
|
rpbouman.blogspot.com | ||
| | | | |
www.tocker.ca
|
|
| | | | | ||
| | | | |
avestura.dev
|
|
| | | | | Have you seen this legendary SQL iceberg meme? Let's talk about it while wearing our PostgreSQL hat! | |
| | | | |
www.prisma.io
|
|
| | | | | Databases are, by definition, very good at processing and manipulating information. Learn more about functional units, workflows, and more. | |
| | | | |
jack-vanlightly.com
|
|
| | | Over the past few months, I've seen a growing number of posts on social media promoting the idea of a "zero-copy" integration between Apache Kafka and Apache Iceberg. The idea is that Kafka topics could live directly as Iceberg tables. On the surface it sounds efficient: one copy of the data, unified access for both streaming and analytics. But from a systems point of view, I think this is the wrong direction for the Apache Kafka project. In this post, I'll explain why. | ||
