Join the DZone community and get the full member experience.Join For Free
WSDL sucks. The whole WS-* protocol stack sucks. There, I said it.
It hurts, a pain in the but. Difficult to write and hard to debug. I cannot think of another technology that have wasted more of my time and I have yet to find one person that can give me a clear and concise explanation exactly how to to use it. Allegedly one of the most overengineered technology in the history of computers.
Doing wrong is easy, doing right is hard.
Its bloated. Tooling support is poor and hide necessary complexity. Interoperability is hard. Caching is not an option. Noncompliant with traditional web technology. The wire format is insanely verbose. Backward and forward compatibility is a nightmare. You have to read endless piles of specifications to design anything sophisticated; even sometimes bend over backwards to do the simplest of things. All your are left with is a pile crap to maintain in the end.
WTF? Where is KISS and productivity to be found in this mess?
System integration should not be this hard.
Published at DZone with permission of Kristoffer Sjögren, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
How to Use an Anti-Corruption Layer Pattern for Improved Microservices Communication
A Complete Guide to Agile Software Development
How AI Will Change Agile Project Management
An Overview of Cloud Cryptography