|
|
|
|
|
|
by perfect_kiss
2360 days ago
|
|
|
While bare metal Kafka does really bundle itself with lots of OpEx trouble,
have you ever tried using an orchestrator to manage it ? DC/OS implementation easily shuns out 1. and 2. 3. and 4. are valid points,
but I think in a real life these scenarios
are usually related to cloud service cost optimization,
and I would never recommend anyone running Kafka in a cloud due to these reasons. There one more reason, which was not cited, but poses itself a real killer for cloud Kafka dream AFM: clouds, being prone to all kinds of network interruptions, are not well suited for running Zookeeper ensembles with decent uptime. Disclaimer: I have never tried or used Apache Pulsar, and just examining its documentation after spotting this thread. |
|
|
These can be just as fragile and now you have to learn how to manage the orchestrator. Even Confluent's own Kubernetes operator has issues. There's just too many issues with Kafka's design that hinders easy operations.
> "I would never recommend anyone running Kafka in a cloud"
That's a major problem considering that's where most computing is heading. At this point, running in noisey overloaded cloud environments is a good test of the reliability and durability of a software system. Kafka fails massively here.