Suppose I have a large intermediate infrastructure that links requests between several business components (client applications, network, payments, etc.). The middleware stack is responsible for orchestrating, routing, transforming and other materials (similar to Gregor Hohpe's Enterprise Integration Patterns book).
My question is: is there a good design to host business logic on middleware?
Let's say my application A requests some client data from middleware. But in order to get this data, I have to provide a client identifier and some other parameters. Should this parameter be obtained by the requesting application or middleware responsible for “facilitating” and providing an interface that receives client identifiers and selects another parameter internally?
I understand that this is not an easy question (due to the definition of business logic), but I was wondering if this is a general approach or some recommendations.
source
share