5 ms·

WSDL, JSON-WSP[1], now protobuf, and many more formats abound on the web. In the spirit of 'choose the boring technology', which of these[2] is common enough /

WSDL, JSON-WSP[1], now protobuf, and many more formats abound on the web. In the spirit of 'choose the boring technology', which of these[2] is common enough / flexible enough to be worth learning to use and use well for non-fad web development / homestyle programming? I'd default to WSDL since I happened to grow up learning that in school, but I'm sure that's my baby duck syndrome since CORBA etc came before that. [1] https://en.wikipedia.org/wiki/JSON-WSP https://en.wikipedia.org/wiki/JSON-WSP [2] https://en.wikipedia.org/wiki/Interface_description_language https://en.wikipedia.org/wiki/Interface_description_language

ako 6y ago
Maybe have a look at OData, strongly typed data model, standardized query language, selection of data required to optimize performance (similar to graphql), changelist support to enable caching, grouping to enable aggregating large amount of timeseries data, capabilities model so services can indicate what they do and do not support, and support for operations/actions, all conforming to REST.
techbio 6y ago
Thanks for "baby duck syndrome." https://en.m.wikipedia.org/wiki/Imprinting_(psychology) https://en.m.wikipedia.org/wiki/Imprinting_(psychology)
qppo 6y ago
One day we're going to just return to c structs and live with it.
therealmarv 6y ago
wait... I also learned WSDL... is it still a thing? I thought this is SOAP related technology only...
- foolfoolz 6y ago
  when you use these open api generators or protobufs the transport is abstracted away. yes wsdl is soap and POST for everything, but when it’s abstracted away, does it really matter? the value is from not having to think about the transport layer at all
BaronSamedi 6y ago
My first thought when reading the article was, how about CORBA? The author makes no attempt to explain why CORBA and SOAP/WSDL failed so their recommendation has very little merit. Software technology historically follows a pattern: "worse is better". We might also call this pattern "commodification". HTTP/JSON has likely reached the lowest common denominator sweet spot to ensure its success and dominance.

ako 6y ago

Maybe have a look at OData, strongly typed data model, standardized query language, selection of data required to optimize performance (similar to graphql), changelist support to enable caching, grouping to enable aggregating large amount of timeseries data, capabilities model so services can indicate what they do and do not support, and support for operations/actions, all conforming to REST.

techbio 6y ago

Thanks for "baby duck syndrome." https://en.m.wikipedia.org/wiki/Imprinting_(psychology) https://en.m.wikipedia.org/wiki/Imprinting_(psychology)

qppo 6y ago

One day we're going to just return to c structs and live with it.

therealmarv 6y ago

wait... I also learned WSDL... is it still a thing? I thought this is SOAP related technology only...

foolfoolz 6y ago
when you use these open api generators or protobufs the transport is abstracted away. yes wsdl is soap and POST for everything, but when it’s abstracted away, does it really matter? the value is from not having to think about the transport layer at all

BaronSamedi 6y ago

My first thought when reading the article was, how about CORBA? The author makes no attempt to explain why CORBA and SOAP/WSDL failed so their recommendation has very little merit. Software technology historically follows a pattern: "worse is better". We might also call this pattern "commodification". HTTP/JSON has likely reached the lowest common denominator sweet spot to ensure its success and dominance.