3 ms·
soap was a really good interoperability protocol for adding kilobytes of overhead to simple text based rest rpc where interoperability was defined as being able
by a-dub 6y ago
soap was a really good interoperability protocol for adding kilobytes of overhead to simple text based rest rpc where interoperability was defined as being able to interoperate with clients and servers from the exact same software environment.
trying to get perl to talk to windows or windows to talk to java or java to talk to perl never really worked at all.
but wsdl was like this tempting thing. self describing services! (that only worked when you had a full definition of the service on the client side anyhow)
i'd take a wild bet that this stuff at amazon grew out of frustration with soap a long time ago...
edit: read new replies to thread. this is new as of 2018. soap was circa 2002. ah, well.
- oblio 5y agoApparently this is V2 or even v3 of something internal. So probably V1 did what you were saying :-)
- mtdowling 5y agoYup. Smithy is from a lineage of internal tools that have been in use at Amazon since the early 2000s. From my dive into software archaeology at Amazon (I work there), there was a bit of SOAP in use in the 2000s, and some other internal model formats that are now obsolete claimed to be SOAP like. As the years went on, other internal formats came out to replace other formats, until the internal model format became something distantly inspired by SOAP, but very practical and tuned for cross language code generation so it could power AWS (that’s my take at least). That was in use for well over a decade before we built Smithy to improve on and open source the internal format.