We received a support ticket asking about the best way to handle service-to-service communication when upgrading from Broadleaf 2.0.2 to 2.2.1. Specifically, the team wanted a way to call other services that works seamlessly whether the target API is co-located in the same flex package or running as a separate remote microservice.
To address this situation, we’ve introduced (and further enhanced) the Interlink provider approach. Interlink provides a single, unified structure for calling other services, abstracting away the underlying transport mechanism.
Details on interlink can be found at the official documentation here: Interlink Requests - Broadleaf Dev Central