{"id":3569,"date":"2023-03-24T11:37:23","date_gmt":"2023-03-24T10:37:23","guid":{"rendered":"https:\/\/www.architecturemaker.com\/?p=3569"},"modified":"2023-03-24T11:37:23","modified_gmt":"2023-03-24T10:37:23","slug":"what-is-an-event-in-event-driven-architecture","status":"publish","type":"post","link":"https:\/\/www.architecturemaker.com\/what-is-an-event-in-event-driven-architecture\/","title":{"rendered":"What is an event in event driven architecture?"},"content":{"rendered":"

An event is a change of state that is detected by an event-detection system and that may trigger a corresponding action.<\/p>\n

In an event-driven architecture, events are generated by event sources, which are usually applications or devices. Event consumers, which are usually also applications or devices, respond to the events. In many cases, the event sources and consumers are different applications or devices.<\/p>\n

Events can be generated by internal or external sources. Internal events are generated by changes in the state of an application or device, such as a button being pressed or a file being created. External events are generated by changes in the state of the world, such as the arrival of a new email message or the stock price of a company changing.<\/p>\n

In event-driven architecture, an event is an occurrence that is of interest to one or more components in the system. A component can register to be notified when an event of interest occurs. When the event occurs, the event notification is sent to all components that have registered to receive notification of that event.<\/p>\n

What is an event channel in event-driven architecture? <\/h2>\n