Announcement Announcement Module
Collapse
No announcement yet.
War stories on architecting the current logic into Spring integration Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • War stories on architecting the current logic into Spring integration

    Hi all,

    I am looking for some war stories which the community would share.

    I am using Spring Integration as the centerpiece of our SOA architecture, in that it would drive the event driven message and typical HTTP communication.

    However, I found that implementing any existing flow to SI, the flow will become large and convoluted.

    1. What is the experience and the recommendation on tackling an existing flow to SI? How to moduleize the flow other than breaking the flow and importing them?

    2. By importing the flow to a big flow, we lost the "big picture" in STS, because it seems that STS doesn't automatically include the imported flow.

    3. How is a larger project being organized in SI? Chaining the flows?

    4. I think null check is still very valid - a lot of legacy code return null to the SI. It's not easy to express if null payload, do this else that.

    Any thoughts are welcomed.
Working...
X