I once tried to get REST apis adopted in an enterprise setting (as part of a tiny Ruby team). Talking to people in Java and .NET teams soon revealed why there w

I once tried to get REST apis adopted in an enterprise setting (as part of a tiny Ruby team). Talking to people in Java and .NET teams soon revealed why there was outright hostility to REST apis: - lack of knowledge about REST - poor support (if any) for REST apis compared to SOAP in the vendor tools. Of course, getting .NET and Java services and clients interoperating with each other using SOAP was always problematic - but the teams I spoke with tended to work within pretty vertical technology stacks and services. So it was Java clients talking to Java services, or .NET clients talking to .NET services. So they saw SOAP as a good, familiar solution.