DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
Building Scalable Real-Time Apps with AstraDB and Vaadin
Register Now

Trending

  • Designing a New Framework for Ephemeral Resources
  • Implementing RBAC in Quarkus
  • Zero Trust Network for Microservices With Istio
  • Generics in Java and Their Implementation

Trending

  • Designing a New Framework for Ephemeral Resources
  • Implementing RBAC in Quarkus
  • Zero Trust Network for Microservices With Istio
  • Generics in Java and Their Implementation
  1. DZone
  2. Software Design and Architecture
  3. Integration
  4. WSDL vs REST/JSON — The Troll Fight

WSDL vs REST/JSON — The Troll Fight

Long live REST/JSON!

Thomas Jardinet user avatar by
Thomas Jardinet
CORE ·
Nov. 25, 19 · Opinion
Like (10)
Save
Tweet
Share
15.89K Views

Join the DZone community and get the full member experience.

Join For Free

For many years, I have known integration via WSDL, only to see the REST/JSON trend appear with false good reasons and real unknown reasons. 

Contrôle, Gnome, Troll, Créatures Mythiques

WSDL vs REST/JSON — The Troll Fight

Why so Much Hate on WSDL?

WSDL offers a very strict interface contract, where any failure to comply with this contract generates errors. This means that when you want to add a field, if one of the two integration stakeholders has integrated the new field "too early," nothing works anymore. Of course, that's when your WSDL library is the same on both sides because how many times could we not integrate anything because we had two different engines on both sides? I'll let you imagine the meetings when we had to find a solution...

You might also like:  Understanding WSDL

So, of course, we found ourselves rereading the WSDL, and that was the tragedy because the WSDL is completely unreadable. XML, for which you have to define types, operations, namespaces, and then you could hope to start understanding..in XML...very verbose. Oh yes, all defined in the end in several files. Good luck with that.

Why Did REST/JSON Appear?

Not being a computer historian, I can't explain what the exact trigger for REST/JSON's fashion would be, but its gain in popularity is quite correlated with the popularization of the smartphone. Indeed, the size ratio between JSON and WSDL is quite high, which allows a faster response time on networks that can be slow. But it is also the awareness of the ease and flexibility that REST/JSON brings.

Another reason, for me, and this is not very well said, is the rise of agility. Indeed, as described above, if an actor makes a modification in a WSDL, then nothing works anymore. The WSDL is based on waterfall methods, where it is necessary to contract in advance of the phase to carry out tests at the end of all developments. On the other hand, JSON allows supporting modifications as they happen, leaving each team time to implement this damn new field.

Conclusion

In short, it has become anachronistic in my opinion to use the WSDL. Need for agility, understanding, flexibility, readability, and performance. There are no true good reasons to use WSDL anymore! The only case where the use of WSDL still makes sense is where the integration is between two companies and is subject to a strong legal contract in terms of commitment — to protect themselves. In other words, it is a weak argument, which will not remove you from the difficulties inherent to the WSDL.

Long live REST/JSON!

Further Reading

REST vs SOAP — A Few Perspectives

Designing REST API — What Is Contract First?

Integration JSON REST Web Protocols Ease (programming language) teams Testing Interface (computing) SOAP Data Types

Opinions expressed by DZone contributors are their own.

Trending

  • Designing a New Framework for Ephemeral Resources
  • Implementing RBAC in Quarkus
  • Zero Trust Network for Microservices With Istio
  • Generics in Java and Their Implementation

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com

Let's be friends: