A professional YAML engineer specialising in Operations, Kubernetes Continual Integration and Continual deployment tooling person who enjoys writing go, running slowly and putting gifs in slack
One thing to be aware of with event patterns\message bus solutions is that ordering is a fun and often painful assumption.
Most message solutions cannot guarantee cross partition message ordering and there are some fun edge cases with parallel\concurrent interfaces. the old joke still applies
central data highway
Also this really sounds like an Enterprise Service Bus with all the same fun problems :p
Carl has been developing, designing, and architecting web applications professionally since 2005. He is passionate about software architecture, C#, and .NET, amongst other things.
Thanks for your comment, and I hope you enjoyed the article.
Ensuring exactly-once delivery is a broker-specific problem, but you are right; that can be challenging, and readers should keep that in mind. We could say the same for cross partition message ordering.
That said, I don't see the central data highway as unique or monolithic. For example, it could be a distributed set of message brokers forming a data mesh. Hopefully, my metaphor did not bring back too many bad memories.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
One thing to be aware of with event patterns\message bus solutions is that ordering is a fun and often painful assumption.
Most message solutions cannot guarantee cross partition message ordering and there are some fun edge cases with parallel\concurrent interfaces. the old joke still applies
Also this really sounds like an Enterprise Service Bus with all the same fun problems :p
Thanks for your comment, and I hope you enjoyed the article.
Ensuring exactly-once delivery is a broker-specific problem, but you are right; that can be challenging, and readers should keep that in mind. We could say the same for cross partition message ordering.
That said, I don't see the central data highway as unique or monolithic. For example, it could be a distributed set of message brokers forming a data mesh. Hopefully, my metaphor did not bring back too many bad memories.