Event-Driven Architecture

GigaSpaces incorporates Event Driven Architecture (EDA) throughout its platform, side-by-side with API-driven functionality. Event-driven data integration pipelines power operational and digital applications by request (via API calls) or with push notifications.

Data integration pipelines enabled by GigaSpaces run in the following modes:

  • Streaming mode: primarily for user transactions and other fast-changing data; triggered by data change at the system of record (usually implemented using a CDC utility) or by the arrival of an event on a message bus on which the pipeline listens.ย 
  • Batch mode: triggered by a scheduled event, indicative of the elapsed time by which that data should be refreshed; used for slow changing data, such as account data and hence may be refreshed just once a day.

Polling and notifications are the underlying methods with which events are supported for the various use cases. To trigger real-time data enrichment such as anomaly detection in a time series, a stream-based pipeline is required; this is easily implemented using polling.ย 

Notifications are more suitable for pushing events out to digital applications. Some operations, for example profiling customers based on their last 30-days activity, may be triggered once a day and may apply to both stream and batch-based pipelines.

Banner

Download the Smart DIH Product Overview

architecture diagram

Data can be consumed by operational and digital applications. Once the data is integrated, and the enriched data is safely written to a Space in one of these methods:

  • Per request using API calls: here the application is proactiveย 
  • Listening to data events: the application is reactive to changes in the data, which could also be combined with business logic

Hereโ€™s an example of an event-based execution:
A retailer wants to approach those customers whose birthday occurs in the upcoming week with special offers. Using APIs, the application will periodically query the Space for updated data about customers who match that criterion. An offline batch job will likely process the information, although the result will be a push notification through an SMS, email, or mobile app. Using events, the application will be automatically triggered for every customer who matches the criterion.

To assist application developers implementing event-driven logic, GigaSpaces offers a low-code Service Creator. Using the Service Creator, the developer may apply both query (API) and event-based logic, incorporated into a single service.

Smart DIH provides a single interface that listens for events, regardless of the listening method being used, hence decoupling between the listening mechanism and the logic of what to do upon event occurrence, as implemented by the consuming microservice.

Oops! Something went wrong, please check email address (work email only).

You can unsubscribe from these communications at any time. For more information on how to unsubscribe, our privacy practices, and how we are committed to protecting and respecting your privacy, please review our Privacy Policy.