Skip to main content

Performance Considerations

The choice of integration approach has a direct impact on the performance of customer order lookups at the POS.

Events Approach​

When using the events approach, Hii Retail stores customer order data internally. This means:

  • GET performance is controlled by Hii Retail -- the service can be optimized to ensure low latency and high throughput, regardless of the external system's performance characteristics.
  • Scalable for peak loads -- the service can be tuned to handle high volumes of customer orders during peak times without dependency on external system capacity.

Proxy Approach​

When using the proxy approach, every GET request is forwarded to the external system in real time. This means:

  • GET performance depends on the external system -- any latency or downtime in the external system directly affects response times at the POS.
  • User experience impact -- slow responses from the external system can create the impression that the Hii Retail POS is performing poorly, even though the bottleneck is the external system. Store associates and customers may not be aware that the delay originates from the external integration.
  • External system responsibility -- it is important for the external system to ensure that their GET endpoints are optimized and can handle the expected request volume to avoid degraded performance at the POS.