←back to thread

15 points fleshgrinder | 1 comments | | HN request time: 0.221s | source
Show context
temporarely ◴[] No.40919338[source]
The issue with all 'drop in replacements' for Kafka iirc is that many large scale deployments of Kafka rely on exposed but internal aspects of Kafka. Do they also replicate these aspects?

example: https://stackoverflow.com/questions/56080896/what-are-intern...

replies(1): >>40919490 #
1. akshayshah ◴[] No.40919490[source]
That's a good example! The topics in question are created by the Kafka Streams client library using the standard Kafka APIs, so it works just fine with Bufstream. The Kafka ecosystem takes a thick client approach to many problems, so the same answer applies to many similar Kafka-adjacent systems.

There are, of course, some internal details that Bufstream doesn't recreate. We haven't seen many cases where application logic relies directly on the double-underscore internal topics, though - especially since much of that information is also exposed via admin APIs that Bufstream _does_ implement.