Giving Alphabet Soup a Bad Name

For those of you who have had your fill of standards, you're in good company. In the latest Web services study I just wrapped up for Evans Data, we found that even the early adopters still aren't quite up to speed with the alphabet soup.

For those of you who have had your fill of standards, you're in good company. In the latest Web services study I just wrapped up for Evans Data, we found that even the early adopters still aren't quite up to speed with the alphabet soup. (The 427 developers surveyed were pre-screened to make sure they were involved in Web services.) Granted, some of this stuff is still works in progress, but beyond XML and SOAP, we're seeing a disconnect between theory and practice.

For the top four specifications in the Web services chain - the basic stuff - results tilt in favor of hands-on knowledge, though people are still on the fence with UDDI. (Totals don't add up to 100% because there is also a "somewhat familiar" category I left out.):

Hands-on experience with:
XML: 74% (Don't know XML: 9%)
SOAP: 58% (Don't know SOAP: 17%)
WSDL: 42% (Don't know WSDL: 33%)
UDDI: 33% (Don't know UDDI: 31%)

For additional specifications, however, things tilt the other way:

Hands-on experience with:
Java Message Service (JMS): 24% (Don't know JMS: 43%)
WS-Security: 45% (Don't know WS-S: 55%)
BPEL: 29% (Don't know BPEL: 71%)
ebXML: 39% (Don't know ebXML: 61%)
WS-Choreography: 10% (Don't know WS-C: 65%)








Newsletters

You have been successfully signed up. To sign up for more newsletters or to manage your account, visit the Newsletter Subscription Center.
Subscription failed.
See All