3 ms·
While I agree with your premise that SOAP and WS-* is over-engineered, at the basic (simple SOAP + WSDL) I quite like it. There's a defined contract and you can
by bouke 5y ago
While I agree with your premise that SOAP and WS-* is over-engineered, at the basic (simple SOAP + WSDL) I quite like it. There's a defined contract and you can generate strong-typed clients. I haven't checked in a while, but how is Swagger/OpenAPI in that regard?
- rswail 5y agoI basically loathe code generators in general. :) JSON Schema gives you the equivalent of WSDL. There are various libraries that will take a schema and create the strongly typed objects in the language of your choice. Theoretically, if you have "Code on Demand", your client can ask the server for the code to handle a media type :)
- bouke 5y agoJSON schema describes the format, more like XSD. WSDL is a lot more with definitions of operations, bindings etc.
- morelisp 5y agoREST's fundamental pitch is that for a large class of problems, a good format solves problems more easily than a rich set of operations.
- brabel 5y agoThings like grpc and GraphQL seem to be the descendants of SOAP/WSDL. GraphQL is quite nice as it kind of has the best of both worlds: a strongly typed schema for data and operations, while being fairly close to a simple JSON/HTTP API.