It depends. Essentially Interoperability Productions take care of:
- Parallelization
- Queues / Async
- Error management, mitigation, and recovery
- After-error investigation (Visual Trace / Audit)
- Unified overview of integration flows
For each integration or part of an integration you need to decide if you need these features and usually you do. In that case all you need to do is to develop one or more Business Hosts containing the business logic and as long as they conform to Interoperability Production structure you would automatically get all the above mentioned benefits.
You pay for the convenience with the overhead for messages and queues.
In the cases where some (most) of these conditions are true:
- external system (whatever it is) is reliable - downtime is a scheduled rarity
- external system does not throw errors much
- response time is stable and in the sync realm
- interaction with the system is one simple flow
- integration is extremely highload
You can choose to interface more directly.
Furthermore it's not Interoperability/no Interoperability, but rather a scale of how much you expose as Interoperability Hosts. In your example maybe having only a BO is enough and you can forego the BP?
- Log in to post comments
.png)
.png)
.png)