Integration architecture

I'm developing server-side for mobile movie booking application. Server application should have common API to 2 existing booking systems in cinemas. In the future addition of new booking systems is possible. I don't like writing spaghe开发者_如何学Ctti-code, so application must be component (module) oriented. I'm looking at SOA and Mule ESB, but I have no experience with it. Whether correctly I have chosen a way? May be there are more than one (not ESB/not Mule) good solutions for my task.

PS: Common API must be HTTP/REST. API of booking systems are binary custom tcp protocol and SOAP service.

Thank you.

SOA is fine, but an ESB seems overkill for something like this. For integrating with various booking services a simple gateway should suffice.

You may be able to use Mule ESB with content based routing. That is based on the content of the booking your ESB knows which booking service to send it to. Then adding new booking services can be done by adding new routing rules.

See: http://blogs.mulesoft.org/integration-patterns-content-based-routing/