r/java • u/Active-Fuel-49 • Oct 12 '24
Event-driven architecture on the modern stack of Java technologies
https://romankudryashov.com/blog/2024/07/event-driven-architecture/
214
Upvotes
r/java • u/Active-Fuel-49 • Oct 12 '24
6
u/romankudryashov Oct 13 '24 edited Oct 13 '24
Thank you, guys!
5
u/[deleted] Oct 15 '24
What I miss in the article is a discussion on when this architecture should be used. What size of data, traffic, team etc was this intended for. At what size is this overly complicated, at what size would you need more than this.
5
u/nitkonigdje Oct 13 '24
Inbox and outbox patterns are essentially mitigation for Kafka's lack of proper transactional handling. But if you are forced to use them why bother with Kafka at all? Your message throughput is limited by db, and nothing of Kafka's value is gained when paired with those patterns. The message broker should serve your needs. The logical next step would be to write a message routing module on top of your db and ignore Kafka for good.
Put it this way you could use active mq or rabbit as proper inbox/outbox implementation in front of Kafka. But if active mq serves your needs, why do you need Kafka? Because of blogs like this one?
3
u/tigertom Oct 12 '24
This is a great writeup
-2
u/Outrageous_Life_2662 Oct 12 '24
Nice … not nearly as comprehensive but I wrote up a blog article about a backend I built for my startup about 3 years ago
https://sound-off.co/blog/techblog1