In every distributed system architecture diagram, change the box labeled “Kafka” to “ESB” and immediately “The hot new thing” becomes “The legacy we need to get rid of”. Think about that. #decentralize #SpringOne
12
96
11
229
That would be true if Kafka were an ESB. Kafka is messaging and a message bus. Most technology platforms support messaging and message buses.
1
6
They're certainly different things. However, they apparently have very similar effects on the overall system's architecture.
1
2
Especially if there's biz logic in message listeners; that's pretty much where ESB took the industry--pushing biz into the bus. Listeners shld=port adapters.
I wonder tho if potential scale of a single topic (replication) really is centralized. Sure, it could be, but not a must.
1
1
I‘m just skeptical about the effects on coupling you get from having a centralized piece of infrastructure everyone has to talk to and the semantic one you get from considering changes at low-level infrastructure level (database tables) events.
2
1
Since we are nearby I'd like to discuss to better understand what you mean. For one I don't see Kafka or any similar message bus as being any more a dependency than REST. When are you speaking? I will plan to attend and we can chat.
3
1
Depending on how you arrive at a URI, I suppose. If you use hypertext "all the way in" probably not so much. Conceptually, though, I see Kafka and such streaming approaches, as very similar to Atom feeds. Can you tell me how you see Kafka as different than that?
2
1
I don’t necessarily object to Kafka, in fact we’re using it in many projects. I share @olivergierke’s skepticism about infrastructure that often becomes too powerful for its own good, though.
Sep 25, 2018 · 6:26 PM UTC
1
1


