To clarify, my feelings towards Kafka are from the POV of someone who has had to build a managed service on top of it, which is not the common use case (for which many people seem to be happy with).  Other people may have more positive experiences.<p>In my experience, Kafka is a solid system when you work in its wheelhouse, which is a relatively static set of servers &#x2F; topics, that you add to slowly and deliberately. If you can&#x27;t use something like Kinesis, then its a good choice.<p>In Kafka, programmatic administration is generally an afterthought.  They have APIs for doing things, but they generally involve directly modifying znodes.  Simple things don&#x27;t work or have bugs, deleting topics didn&#x27;t work at all until 0.8.2, and even now has bugs. We&#x27;ve seen cases where if you delete a topic while an ISR is shrinking or expanding, your cluster can get into an unrecoverable state where you have to reboot everything, and even then it doesn&#x27;t always get fixed. Most of the time you are expected to use scripts to modify everything (there&#x27;s a wide variety of systems out there that try to build mgmt on top of kafka).<p>Its dependency on Zookeeper is a pain, and limits scalability of topic &#x2F; partition counts.  Rebalancing topics will reset retention periods because they use the last modified ts of the segment files to check for oldness, meaning if you rebalance often, you need extra disk space laying around. ZK has some bugs with its DNS handling, which affects Kafka if you try and use DNS.<p>It has throttling, but its by client id, what you&#x27;d like in some cases, is to say that a node has X throughput, and have the broker be able to somewhat guarantee that throughput, and create backpressure when clients are overwhelming it.  Otherwise your latency can go through the roof. You also want replication to play nice with client requests, and it doesn&#x27;t (if you add a new broker and move a bunch of partitions to it, you&#x27;ll light up all your other brokers while it replicates, and cause timeouts).<p>Its replication story can cause issues when network partitions come into play.<p>It&#x27;s highly configurable like many Apache projects, which is a blessing and a curse, as your team has to know all the knobs, both consumer &#x2F; producer &#x2F; broker side.<p>The alternative if you are at a company with the resources to do so (mine is), is to build something that fits your use case better than Kafka, or to use a hosted service like this, or Kinesis.