Spring integration flow Design -
this going second project going implement using spring integration. confident architecture after successful release o f first project .but have few clarification required define flow of external calls. in architecture have multiple call database,web service , cache server , have defined these flows in single flow .
scenario 1.
channel- >jdbcoutbound -> router ->splitter ->wsoutbound -> aggregator ->reply channel.
here external service call execute single gateway. these approach or can define separate gate way call below
scenario 2.
seq 1) gateway ->jdbcoutbound -> router ->reply channel. seq 2) gateway(use response seq 1) ->splitter ->wsoutbound -> aggregator ->reply channel
which scenario best ?
it depends of requirements.
as noticed both variants work well. so, big height matter of taste. but... let's take @ useful or noise function in our project!
gateway
designed distribute business , integration logic between separate layers. other side gateway
approach spring's autowiring feature allows have high-level api our integration solution.
so, think bit further if there need expose such high-level api second call.
no reason divide our configuration finely if <channel>
, <service-activator>
(or similar) pair enough reach solution!
from other side it's opinion. you'll find own style experience.
Comments
Post a Comment