Choosing the right integration pattern

Select the integration pattern that best fits your business scenario. The appropriate pattern helps improve performance, scalability, and maintainability.

ION supports multiple integration patterns for exchanging data between applications. Select an integration pattern based on how data becomes available, the required response time, and the capabilities of the source application.

Table 1. Integration pattern guidance
Pattern Use when Typical latency
Scheduled ION API Adapter Periodic synchronization or non-urgent data retrieval. 30 seconds or greater
IMS (Infor Messaging Service) Data is delivered when a business event occurs. Near real-time
ION Event Management Actions or notifications are triggered based on published BODs and business rules. Near real-time

Integration guidance

Use these guidelines when selecting an integration pattern:

  • If the source application can publish events or BODs when data changes, use IMS.
  • If you need to evaluate published BODs and trigger alerts, notifications, or downstream actions based on business rules, use ION Event Management.
  • If data is available only through a request-based API and cannot be event-driven, use the Scheduled ION API Adapter with an interval that meets your business requirements.
Note:  Avoid configuring aggressive polling intervals to simulate real-time integration. Event-driven integration patterns, such as IMS, provide a more scalable and efficient solution.