Explore >> Select a destination
|
You are here 
|
streamnative.io | ||
| | | | |
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. | |
| | | | |
www.confluent.io
|
|
| | | | | Existing Confluent Cloud (CC) AWS users can now use Tableflow to easily represent Kafka topics as Iceberg tables and then leverage AWS Glue Data catalog to power real-time AI and analytics workloads. | |
| | | | |
www.onehouse.ai
|
|
| | | | | Format wars are over. The real innovation? Building data platforms that empower teams to use the right tool for their needs. Discover how an open, flexible approach unlocks innovation and efficiency. | |
| | | | |
endjin.com
|
|
| | | Discover the use of Synapse Notebooks in Azure Synapse Analytics for data analysis, cleaning, visualization, and machine learning. | ||
