Anti-patterns in event-driven architecture
codeopinion.com
Anti-patterns in event-driven architecture
1–10 of 171 posts
Re: Anti-patterns in event-driven architecture
#2Re: Anti-patterns in event-driven architecture
#3Can someone share some long term event driven success stories? Almost everything you see online is written by consultants or brand new, greenfield implementations, curious how long these systems last.
Re: Anti-patterns in event-driven architecture
#4[deleted]
Re: Anti-patterns in event-driven architecture
#5Can someone share some long term event driven success stories? Almost everything you see online is written by consultants or brand new, greenfield implementations, curious how long these systems last.
No. We have a complete fucking disaster on our hands.
Re: Anti-patterns in event-driven architecture
#6Can someone share some long term event driven success stories? Almost everything you see online is written by consultants or brand new, greenfield implementations, curious how long these systems last.
No. We have a complete fucking disaster on our hands.
How old of a system? Do you feel it’s the implementation, the design, or the concept itself that went wrong? Is your system a good fit?
(No stake in this one way or another, just curious.)
Re: Anti-patterns in event-driven architecture
#7[flagged]
Re: Anti-patterns in event-driven architecture
#8Earlier quoted context omitted.
No. We have a complete fucking disaster on our hands.
How old of a system? Do you feel it’s the implementation, the design, or the concept itself that went wrong? Is your system a good fit? (No stake in this one way or another, just curious.)
Less than 5 years. Vanity project. Built and maintained by astronaut architects. Entirely unnecessary. Poorly implemented down to the level of wire contracts being inconsistent. Overheads are insane both from engineering and operational POV.
Re: Anti-patterns in event-driven architecture
#9Can someone share some long term event driven success stories? Almost everything you see online is written by consultants or brand new, greenfield implementations, curious how long these systems last.
Yes, it’s a great tool for integration. We have a product suite and it’s our chosen way to connect products.
Re: Anti-patterns in event-driven architecture
#10Can someone share some long term event driven success stories? Almost everything you see online is written by consultants or brand new, greenfield implementations, curious how long these systems last.
I was the lead developer on one for an insurance company a few years back, and it’s still in active use. Insurance is a heavily regulated domain, where an audit trail is more important than performance. There was a natural pattern for it to follow, as we were mapping a stable industry standard.
I also tried doing it in a property setting, where profit margins were tight. The effort needed wasn’t worth the cost, and clients didn’t really care about the value proposition anyway. We pretty much replaced the whole layer with a more traditional crud system.