Solved: Should I push for proxy REST/JSON even if target i... - Page 2

vinhpham95 · 08-19-2019 02:27 PM

Target expects SOAP/XML. Source can do REST/JSON or SOAP/XML. Should I tell Source to call REST/JSON and transform payload into SOAP/XML via. Apigee, or should I just tell Source to keep it SOAP/XML for consistency?

Based on Best Practices, REST/JSON is the ideal solution for (most) Proxies. However, does this still apply if target has a requirement for SOAP/XML - that is, if the target application expects SOAP/XML, should I still ask the source to send me via. REST/JSON?

nagashree_b

You said it all!

Based on Best Practices, REST/JSON is the ideal solution for (most) Proxies.

Its is ideal to have the consumer of your API make a REST call with JSON if you are undergoing a modernization exercise. However if you see some resistence to change from the consumers, you could start off with supporting both XML and JSON by branching out the logic using the content-type header and send the responses in appropriate format based on the Accept header in the request.

You could run it this way for sometime (or even indefinite) and then have a newer version mandate REST/JSON.

View solution in original post

Should I push for proxy REST/JSON even if target is SOAP/XML?