Great conversation. Really eye opening when thinking about the bigger picture and the dependency that gets created if the choice of having Kafka as the source of truth is made. This without even going in to the actual implementation overhead that comes from working with Kafka on some scenarios. I've started thinking of Kafka as a log more than a broker. The persistence is nice, but the added complexity on the consumer side due to the "dumb broker" model just didn't fit the bill for my use case. Nice shiny and powerful tool, but nothing is a silver bullet and everything comes at a cost. You just have to pick your poison in the end.
@ErikWilde
2 жыл бұрын
Exactly. It's a nice tool but one that comes, like all tooks, with side-effects snd constraints. And since it's so simple you can use it in many different ways. I tend to ignore the persistence, but that's because I see it mostly as a broker.
@mindhoc
Жыл бұрын
pure gold, i want to hear more
@ErikWilde
Жыл бұрын
Thank you, I'll ask Eberhard! ;-)
@kevinfleischer2049
Жыл бұрын
It would be worth to discuss the different strategies for event-Design. First of all "what is an Event" and secondly "what data should be inside an Kafka-Event". Eberhard told that one customer just adds "everything they have" into an Event. Alternatively you could do the opposite: Just write the "type" + the Key Identifiers. And all the attached Consumers have to know the corresponding data that is important for them.
@rahulsood81
Жыл бұрын
There's no context built up as part of the discussion. Everything seems so abstract, that only these experts can understand.
Пікірлер: 6