6 ms·
> aside from the viewpoint of it being one more external dependency This is exactly the point. One more dependency, one more executable. Redpanda get rid of th
by voctor 6y ago
> aside from the viewpoint of it being one more external dependency
This is exactly the point. One more dependency, one more executable. Redpanda get rid of that.
- ckdarby 6y agoKafka also has a KIP to get rid of Zookeeper and I see a bunch of the issues related to the KIP resolved and looks like it should be happening this year. Doesn't this just internalize the dependency within the project itself? Isn't Redpanda taking on all the effort that Zookeeper has been doing for years, all the edge cases, all the additional support and now the coupling of it within the very project itself?
- agallego 6y agowe have exactly 1 replication protocol. That's raft. We spend a ton of time ensuring it's correctness 1. https://vectorized.io/validating-consistency/ https://vectorized.io/validating-consistency/ 2. https://vectorized.io/kafka-redpanda-availability/ https://vectorized.io/kafka-redpanda-availability/ That is our essential complexity. If you are trying to replicate data to machines, you need to replicate data to machines. We chose raft as the only way. In essence we are much simpler than upstream w.r.t protocols for data replication.