title: Spring integration flow vs regular service and adapter
body: <p>I had some legacy code that had SOAP services. Now I am building Rest API for some objects that may call one or more SOAP operation. I was looking into Spring Integration. From the <a href="https://projects.spring.io/spring-integration/" rel="nofollow noreferrer">docs</a></p>
  
  <blockquote>
    <p>In addition to wiring together fine-grained components, Spring Integration provides a wide selection of channel adapters and gateways to communicate with external systems.</p>
  </blockquote>
  
  <p>Above statement sounds enticing. I was writing rest microservice controller, Validation service, Rest request to SOAP request mapper and SOAP client. I some cases when there are multiple calls, there is even more code I had to write and I did write the code in many cases. </p>
  
  <p><em>Spring Integration</em> at high level looked like a framework oriented for Async messages. My problem is that the call need to be more or less a synchronous call and performance is critical. Had anyone used <code>Spring integration</code> for this problem and can you share your experiences. </p>