GUI
commented
9 years ago API Umbrella should be able to proxy to existing SOAP services (if you wanted rate limiting, etc for your SOAP services). However, I haven't given much thought to trying to transform SOAP services into REST services on the fly.
Something like this loopback-connector-soap looks like it could potentially do the trick, though. That's a nodejs project which could possibly be integrated with our gatekeeper component, which is also nodejs and is where our custom proxy layer stuff happens. However, I'm not sure integrating that kind of server component into the reverse proxy layer totally makes sense. But you could always setup something like loopback-connector-soap (or any other soap transformation server) as an independent service and then just point to that service as another API Backend that gets configured in API Umbrella. Does that approach make sense and would that meet your needs? That would decouple the SOAP transformation from API Umbrella, but were you looking for something more tightly integrated with API Umbrella to accomplish this?
What are your thoughts on integrating/bridging SOAP and REST interfaces? E.g. some older APIs were designed when SOAP was more prevalent, and now may wish for REST interfaces. On what levels would a SOAP / REST bridge exist in the API tooling?