[incognito_limey]

Why is (no, kafka is never the answer)?

[KaiserPro]

Large, painful to configure, high latency and difficult to look after.

[incognito_limey]

Not sure I understand the "large" comment. Painful to configure.. have you looked at CP-Ansible: https://github.com/confluentinc/cp-ansible

High Latency: Kafka's latency depends on your configuration and infrastructure. It has some of the lowest latency out there when configured correctly.

Curios to know why you find it difficult to look after? It's super stable, and is pretty easy to monitor via JMX.

[isugimpy]

Curious to hear more details about your thoughts on this. I've done some pretty significant improvements around my team's use of it in the last few months and can't say I've had this experience. The difficulties with it really, to me, seem to be a case of batteries-not-included, speaking as someone who had never run it prior to last August.

[dominotw]

> difficult to look after.

Agree with this 100%. But what about hosted kafka solutions?

> high latency

Not sure I understand this point.

[incognito_limey]

What makes it difficult to look after? Genuinely curious. I've run it in production for years and its been pretty solid.

[wdb]

What are good Kafka alternatives? There got to be some Go written one somewhere ;)

[thayne]

NATs is one. Although it has some limitations.