Limitations associated with Web Services
Despite its popularity and relative simplicity, SOAP has several limitations, which in turn affect the Web services directly, relying on these resources.
The limitations of web services are described below:
- Security and privacy – all versions of SOAP defines any type of security. This is due to SOAP using HTTP, but to implement security mechanisms within the network can use SSL over HTTP (also known as HTTPS) to ensure the confidentiality, integrity and authentication of the client, server and encrypted communication.
As there is no support for security, which includes privacy standards that make Web services, each project has led to seek different solutions to solve the security problem which becomes incompatible with the promise to implement a global standardization.
Comments and routing – to support the asynchronous messaging features of traditional:
- Quality of service and reliability – to ensure response times and detect exceptions
- Transaction processing – to support communication transaction to associate the communication transaction with the local transactions and to participate in distributed transactions
- Management – to monitor the status and behavior of Web Services
- Performance – to optimize the delivery of Web services that have implications for the design of applications, remote calls, the network and storage / processing of documents
- Interoperability – support interoperation without problems is the ultimate goal of Web services and SOAP provide a platform for integration between applications and different languages and deployed on any operating system.
Technologies Used In Web Services
For the representation and structuring of data in the messages received / sent is used the XML (extensible Markup Language). Calls to operations, including input / output, are encoded in SOAP (Simple Object Access Protocol, XML-based). Services (operations, messages, parameters, etc.) are described using WSDL (Web Services Description Language).
Extensible Markup Language (XML)
Extensible Markup Language (XML) is the basis on which Web services are built. XML provides the description, storage, transmission format to exchange data through Web Services and also to create Web Services technologies to exchange data.
The syntax of XML technologies used in Web services specifies how data is represented generally define how and with what qualities of service data is transmitted, details how the services are published and discovered. Web Services decode the various parts of XML to interact with various applications.
Simple Object Access Protocol (SOAP)
SOAP is based on a remote invocation of a method and for this you need to specify the address of the component, the method name and arguments to this method. These data are formatted in XML with certain rules and usually sent by HTTP for this component. Not define or impose any semantics, whether the programming model, whether the semantics of the specific implementation. This is extremely important because it allows either the service or the client that invokes the service applications are developed on different programming languages.
For this reason, SOAP has become an accepted standard for use with Web Services, a technology built on XML and HTTP. Thus, it is intended to ensure interoperability and intercommunication between different systems through the use of XML and HTTP transport mechanism or another, for example, SMTP. SOAP allows XML documents to send or receive on the Web support a common protocol for transferring data to an effective communication network, i.e., SOAP provides transportation data to Web Services.
For Web, SOAP is an RPC protocol that works over HTTP (or SMTP, or other) to overcome the limitations of security / firewalls usually imposed on the traditional RPC (RMI, DCOM, CORBA / IIOP) supporting XML messages. Instead of using HTTP to request an HTML page to be viewed in a browser, sends a SOAP message using the XML HTTP request and receives a response, if any, through the HTTP response.
To ensure smooth transmission of XML message, the HTTP server such as Apache or IIS (Microsoft Internet Information server) receives SOAP messages and to validate and understand the format of the XML document defined in the SOAP v1.1.
Continued…
Related posts:
- Web Service Solutions | Part 1
- Web Service Solutions | Part 2
- Web Service Solutions | Part 4
- Windows Web Hosting Solutions
- Linux Web Hosting Solutions
- Secure Ecommerce Web Hosting Solutions
- Business Web Hosting Solutions – Basics
Tags: Limitations associated with Web Services, technologies used in web services, web service solutions