Event-based integration refers to a method of processing that is triggered by the occurrence of specific external events rather than being executed on a fixed schedule. In this approach, integration processes continuously “listen” for particular events, and when such an event occurs, it triggers the associated processing tasks. This model is particularly useful for handling irregularly occurring events that require immediate action or response.
Key Characteristics of Event-Based Integration:
- Real-Time Processing: Events are processed as they occur, allowing for immediate responses to changes in the system or environment.
- Decoupled Systems: Event-driven architectures enable systems to operate independently, reducing dependencies between components.
- Scalability: This approach can efficiently handle varying loads and spikes in event frequency without significant performance degradation.
- Flexibility: Organizations can easily adapt to new business requirements by adding or modifying event listeners and handlers without disrupting existing processes.
The following advanced optional features facilitate the building, deployment, and management of event-driven integrations:
- Services Enablement — Lets you turn any integration process into a web service that can then be deployed on premise or in Boomi’s runtime cloud. A Runtime’s shared web server accepts HTTP and SOAP requests in real time and initiates processing. The requests are the events upon which integration is based. The web server can be configured at the account and account user level to control network and security settings.
- API Management — Builds upon Services Enablement, enabling a web service publisher to expose versioned APIs for logical groups of web services. A web service API consists of a set of REST, SOAP, and/or OData endpoints. APIs are implemented in Integration as deployable API components.
- Event Streams — Boomi Event Streams is a cloud-native, event-driven, message queueing solution built into the Boomi Enterprise Platform, making it easy to create high-performance, scalable, event-driven connections for demanding integration use cases.
- Runtime Message Queuing — Runtimes support message queuing. The presence in of a messaging system is essential for facilitating inter-process communication, a key requirement for many types of event-based integration usage scenarios. Simplicity, robustness, and reliability are major advantages of the Runtime’s native support for message queuing.
- Many usage scenarios for Runtime message queuing involve the use of the Runtime’s shared web server. An understanding of web service API management is therefore helpful for deriving the benefits of Runtime message queuing.