zlacker

It is as good as any if you have no financial constraints and no technical overhead and time constraints, but everyone does.

Kafka is one of those systems that needs to be justified by out-scaling other solutions that don't come wedded with all its baggage.

>>weego+(OP)
What would you say is its baggage?

>>hansbo+F
For me, the baggage is mostly the complexity of the service. With that comes monitoring, maintenance, tuning, debugging and troubleshooting.

Lessened somewhat with SaaS products like Amazon Kinesis (technically not a Kafka, but close).

Another "baggage" is that an event-driven setup is eventual-consistent -and async- by nature. If your software already is eventual-consistent, this is not a problem. But it is a huge change if you come from a blocking/simple "crud" setup.

>>berkes+Js
I second Kafka having massive operational overhead. It's a burden and is killing any support for it within our org.