The test of Web service awaiting practice

Web|web Services SOAP,WSDL, and UDDI Define Web services in XML, but they are not guaranteed to benefit components in the software architecture. To apply Web services, protocols need to be clearer, tools need to be more useful, and it project managers and developers need to change their minds.

But the benefits of Web services in communications, such as reusable components and the ease of integration in enterprise applications, have made Microsoft and IBM marvel at its efficiency. Although the application of Web services is still in the experimental phase, the media has taken these advanced concepts into the hearts of all. Although developers and opponents disagree, they all get a lot of opportunities from Web services.

There are some bugs that developers find in Web services, some of which are resolved, and the rest are not:

Security and identification
Of all the flaws in Web services, these two points are the first and most frequently mentioned. Fortunately, when you're dealing with sensitive data, you can use the SSL Web encryption tool to better prevent your XML information from being tapped, but it's another thing to authenticate XML documents on the server. There are six kinds of authentication schemes between different standards committees, trying to solve the problem by numerical characteristics. But it will take some time for the criteria to be determined.

Completion of the transaction
Like a supply chain, when there are many parties involved, the transaction becomes longer and more complex. This requires finding a way to monitor complex transactions so that all parts of the process can be identified. Some standards, including the Security Statement identification language (secure assertion Markup Language), the Business Transaction protocol (Business Transaction Protocol), and IBM's HTTP, have been introduced to address this issue, But the standards Committee has not yet demonstrated them.

Perform
There is no good solution to the problem. XML on HTTP solves this problem somewhat easily. In its security protocols, users cannot respond quickly to specific actions. In addition to the slow credit card testing that the user expects, other potential problems can make it possible for Web services to be used within the enterprise's internal projects and automated business-to-business transactions.

Higher dependencies
When multiple applications are dependent on a Web service, any changes to the Web service will cause the application to fail. Similarly, the popularity of personal Web services requires close monitoring of hardware to ensure that they are working properly. And when programmers try to predefined a feature for future applications, as with any building part, the components of a Web service also need to be named uniformly.

Effectiveness and reliability
Web joins may be more reliable than before, but when you access components through a firewall, you have to endure long waits. You also have to trust these components, in fact, they are black boxes that access the XML API. So companies have to build old trust relationships before they are worth the risk of applying Web services.

Additional development efforts
Anyone likes the right way to build applications: complete documentation and maximum reusability. In fact, the project needs to be completed on time and within budget. The first time you use the components provided by a Web service to build your application requires extra effort and time, but in any case, many IT project managers do not want to postpone the completion of the project because they can benefit from reusability later. Similarly, it is very unlikely that an IT project manager would make the application more beautiful by making it a component of his application. Even the components of a Web service can benefit other applications.

But none of these flaws is completely certain, and in fact, the developers I see agree with the direction of Web services, many of whom are hosting project development.

We should now have a clear understanding of the limitations of Web services, and we should have a realistic estimate of the time and effort we need to get these benefits. Perhaps unlike many other technologies, this promising technology can avoid being given too much expectation.
Go