Either way the point is if the REST and SOAPY endpoints both share the same model, we could obviously extend the composition idea I introduced in my last post to allow composition across these two types of services.

But now you are starting to see some real power.

You can have a very limited set of SOAP Service Operations, and allow for almost infinite composability simply by opening up a couple of Astoria style REST endpoints. You can use those REST endpoints as parameters to your SOAPY service operations.

This combines the flexibility of REST with the tight contracts of SOAP without a lot of the latency.