As today most of the development is towards the lightweight service and RESTful architecture, is WSDL still needed to describe these services? In today's world -- where cloud computing, mobile computing, and Internet of Things are dominating -- is WSDL and UDDI still used by industry or practitioners?
closed as primarily opinion-based by Robert Harvey, gnat, BobDalgleish, 8bittree, Laiv Sep 29 '17 at 8:51
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
A wsdl is just a contract saying this is how you can call this service. Of course you also have (Json) webapi endpoints that don't have a formal description these days (and you could with odata you get a wsdl-ish metadata description) However soap services with a wsdl still have it's place. A new trend doesn't mean there isn't a use case for the old way.And don't forget many companies still have legacy systems.
So yes it's still being used.