Implementing an event-driven architecture (EDA) is a road riddled with challenges. Among them is choosing the right tooling for the job. Many event-driven tools seem quite similar, at least at first glance, and you’d expect they could be used equally well for the same purposes. But that’s often not the case and choosing the solution best suited to your needs can be tricky. By Tun Shwe.
Article focuses specifically on message queueing and event streaming, highlighting their differences, common denominators and suitability for various use cases:
- Understanding messages queues and event streams
- Message queueing vs. event streaming tech: Comparing capabilities
- Message queueing and event streaming use cases
- Message queueing is sometimes a stepping stone to event streaming
If you’re dealing with small and medium workloads, you’re looking to reliably and flexibly route messages between components and your system is primarily interested in the current state, a message queueing technology is an adequate choice.
On the other hand, if you want to handle high-volume, high-frequency event streams in a scalable and reliable way, you need to do complex processing on data as it arrives to gain actionable real-time insights and your system is concerned not only with the current state, but a historical record of state changes, then event streaming is the right way to go. Nice one!
[Read More]