Explore >> Select a destination
|
You are here 
|
blog.brokennetwork.ca | ||
| | | | |
techwithdave.davevw.com
|
|
| | | | | Taking the information from Jim Butterfield's interactive program we can determine a few optimal choices for configuring the location of v... | |
| | | | |
www.jamieweb.net
|
|
| | | | | Installing and configuring the Quagga network routing software suite and establishing a BGP peering session to exchange routing information. | |
| | | | |
anuragbhatia.com
|
|
| | | | | ||
| | | | |
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. | ||
