The polling system acts like the impatient customer. In a commerce-related scenario, it keeps polling the system for new updates such as orders and payment authorizations while the event driven system relies on asynchronous event handlers to notify it of updates in the system. By Sajjad Heydari.
Event based systems in computer science go back to the 1950s where they were first designed to handle asynchronous events such as Input/Output. Edsger Wybe Dijkstra designed the first interrupt handler on the Electrologica X-1 that is still used in modern systems to this day. The modern day’s events are the same concept, only they are used in different environments.
The event driven system is easier to develop and more efficient, but it requires special infrastructure to work. The good news is that some software and platforms like Fabric support event driven systems. In commerce, these systems create more streamlined operations so customers get their orders faster.
The article then describes:
- Example of an event driven system
- Parts of an event driven system
- The event
- The event router
- Benefits of event driven systems
In this post we provided an overview of how event driven systems streamline commerce. For a more detailed view of how events and event routers allow different services to communicate better in a commerce tech stack, check out thisvideo from AWS. Nice one![Read More]