I am pleased to announce that HK Airport Authority has awarded the Event Broker contract to E Tag to deliver a Solace Event Broker for HK Smart Airport's EDA establishment. Event Broker provides a unified foundation for the distribution of events to HK airport to improve safety, customer experience and operational efficiency by routing event-driven data between customer touchpoints and applications.
Request-Response vs Event-Driven APIs
At its core, "Request–Response" is a message exchange pattern in which a requestor sends a request message to a replier system. The replier system receives and processes the request, and if all goes well, it returns a message in response. For e.g. REST
In an "Event-Driven" architecture, applications integrate multiple services and products as equals based on event-driven interactions. These interactions are driven by event emitters, event consumers, and event channels, whereby the events, themselves, are typically significant ‘changes in state’ that are produced, published, propagated, detected, or consumed. The advantage is that an event emitter does not need to know the state of the consumer, who the consumer is, or how the event will be processed (if at all). It is a mechanism of pushing data through a persistent stream.