Web Services:

A web service makes software application resources available over networks using
standard technologies. Because web services are based on standard interfaces, they can
communicate even if they are running on different operating systems and are written in different
languages.

A Web service is a method of communication between two electronic devices over a

network. It is a software function provided at a network address over the Web with the service
always-on as in the concept of utility computing. Many organizations use multiple software
systems for management.

Web services are of two kinds: Simple Object Access Protocol (SOAP) and
Representational State Transfer (REST).

Web Service is can be defined by following ways:

o It is a client-server application or application component for communication.

o The method of communication between two devices over the network.
o It is a software system for the interoperable machine to machine communication.
o It is a collection of standards or protocols for exchanging information between
two devices or application.

Types of Web Services

There are mainly two types of web services.

1. SOAP web services.

2. RESTful web services.
Web Service Features
XML-Based
Web services use XML at data description and data transportation layers. Using XML
exclude any networking, operating system, or platform binding. Web services-based
operation is extremely interoperable at their core level.

Loosely Coupled
A client of a web service is not fixed to the web service directly. The web service
interface can support innovation over time without negotiating the client's ability to
communicate with the service. A tightly coupled system means that the client and server
logic are closely tied to one another, indicating that if one interface changes, then
another must be updated. Accepting a loosely coupled architecture tends to make
software systems more manageable and allows more straightforward integration
between various systems.

Coarse-Grained
Object-oriented technologies such as Java expose their functions through individual
methods. A specific process is too fine an operation to provide any suitable capability at
a corporate level. Building a Java program from scratch needed the creation of various
fine-grained functions that are then collected into a coarse-grained role that is
consumed by either a client or another service.

Businesses and the interfaces that they prove should be coarse-grained. Web services
technology implement a natural method of defining coarse-grained services that
approach the right amount of business logic.
Ability to be Synchronous or Asynchronous
Synchronicity specifies the binding of the client to the execution of the function. In
synchronous invocations, the client blocks and delays in completing its service before
continuing. Asynchronous operations grant a client to invoke a task and then execute
other functions.

Asynchronous clients fetch their result at a later point in time, while synchronous clients
receive their effect when the service has completed. Asynchronous capability is an
essential method in enabling loosely coupled systems.

Supports Remote Procedure Calls (RPCs)

Web services allow consumers to invoke procedures, functions, and methods on remote
objects using an XML-based protocol. Remote systems expose input and output
framework that a web service must support.

Component development through Enterprise JavaBeans (EJBs) and .NET Components

has more become a part of architectures and enterprise deployments over a previous
couple of years. Both technologies are assigned and accessible through a variety of RPC
mechanisms.

SOAP Web Services

SOAP stands for Simple Object Access Protocol. It is a XML-based protocol for accessing
web services.

SOAP is a W3C recommendation for communication between two applications.

SOAP is XML based protocol. It is platform independent and language independent. By

using SOAP, you will be able to interact with other programming language applications.

Advantages of Soap Web Services

WS Security: SOAP defines its own security known as WS Security.

Language and Platform independent: SOAP web services can be written in any programming
language and executed in any platform.
Disadvantages of Soap Web Services
Slow: SOAP uses XML format that must be parsed to be read. It defines many standards
that must be followed while developing the SOAP applications. So it is slow and
consumes more bandwidth and resource.

WSDL dependent: SOAP uses WSDL and doesn't have any other mechanism to discover
the service.

RESTful Web Services

REST stands for REpresentational State Transfer.

REST is an architectural style not a protocol.

Advantages of RESTful Web Services

Fast: RESTful Web Services are fast because there is no strict specification like SOAP. It
consumes less bandwidth and resource.

Language and Platform independent: RESTful web services can be written in any
programming language and executed in any platform.

Can use SOAP: RESTful web services can use SOAP web services as the implementation.

Permits different data format: RESTful web service permits different data format such
as Plain Text, HTML, XML and JSON.

SOAP vs REST Web Services

There are many differences between SOAP and REST web services. The important 10
differences between SOAP and REST are given below:
 No. SOAP REST

1) SOAP is a protocol. REST is an architectural style.

2) SOAP stands for Simple Object Access REST stands for REpresentational State Transfer.
Protocol.

3) SOAP can't use REST because it is a REST can use SOAP web services because it is a concept an
protocol. can use any protocol like HTTP, SOAP.

4) SOAP uses services interfaces to REST uses URI to expose business logic.
expose the business logic.

5) JAX-WS is the java API for SOAP web JAX-RS is the java API for RESTful web services.
services.

6) SOAP defines standards to be strictly REST does not define too much standards like SOAP.
followed.

7) SOAP requires more bandwidth and REST requires less bandwidth and resource than SOAP.
resource than REST.

8) SOAP defines its own security. RESTful web services inherits security measures from th
underlying transport.

9) SOAP permits XML data format only. REST permits different data format such as Plain text, HTM
XML, JSON etc.

10) SOAP is less preferred than REST. REST more preferred than SOAP.

What is WSDL and UDDI in web services?

WSDL is the standard format for describing a web service. WSDL definition
describes how to access a web service and what operations it will perform. WSDL is a
language for describing how to interface with XML-based services. WSDL is an integral
part of UDDI, an XML-based worldwide business registry.

WSDL
WSDL is an acronym for Web Services Description Language.

WSDL is a xml document containing information about web services such as method
name, method parameter and how to access it.

WSDL is a part of UDDI. It acts as a interface between web service applications.

WSDL is pronounced as wiz-dull.

WSDL
WSDL is an XML-based language for describing web services and how to access them.
 WSDL stands for Web Services Description Language.
 WSDL was developed jointly by Microsoft and IBM.
 WSDL is an XML based protocol for information exchange in decentralized and
distributed environments.
 WSDL is the standard format for describing a web service.
 WSDL definition describes how to access a web service and what operations it
will perform.
 WSDL is a language for describing how to interface with XML-based services.
 WSDL is an integral part of UDDI, an XML-based worldwide business registry.
 WSDL is the language that UDDI uses.
 WSDL is pronounced as 'wiz-dull' and spelled out as 'W-S-D-L'.

UDDI
UDDI is an XML-based standard for describing, publishing, and finding web services.
 UDDI stands for Universal Description, Discovery, and Integration.
 UDDI is a specification for a distributed registry of web services.
 UDDI is platform independent, open framework.
 UDDI can communicate via SOAP, CORBA, and Java RMI Protocol.
 UDDI uses WSDL to describe interfaces to web services.
 UDDI is seen with SOAP and WSDL as one of the three foundation standards of
web services.
  UDDI is an open industry initiative enabling businesses to discover each other
and define how they interact over the Internet.

UDDI
UDDI is an acronym for Universal Description, Discovery and Integration.

UDDI is a XML based framework for describing, discovering and integrating web
services.

UDDI is a directory of web service interfaces described by WSDL, containing information

about web services.

What is XML-RPC explain with example?

XML-RPC (short for Extensible Markup Language remote procedure call) is a protocol
specification for executing RPC calls (remote calls in computer networks) using
the stateless network protocol HTTP and the markup language XML, which gives it
part of its name.

What is XML-RPC used for?

XML-RPC is a specification that enables communication between WordPress and
other systems. It did this by standardizing those communications, using HTTP as the
transport mechanism and XML as the encoding mechanism.

What is XML-RPC ?
XML-RPC is among the simplest and most foolproof web service approaches that
makes it easy for computers to call procedures on other computers.
 XML-RPC permits programs to make function or procedure calls across a
network.
 XML-RPC uses the HTTP protocol to pass information from a client computer to a
server computer.
 XML-RPC uses a small XML vocabulary to describe the nature of requests and
responses.
 XML-RPC client specifies a procedure name and parameters in the XML request,
and the server returns either a fault or a response in the XML response.
 XML-RPC parameters are a simple list of types and content - structs and arrays
are the most complex types available.
 XML-RPC has no notion of objects and no mechanism for including information
that uses other XML vocabulary.
 With XML-RPC and web services, however, the Web becomes a collection of
procedural connections where computers exchange information along tightly
bound paths.
 XML-RPC emerged in early 1998; it was published by UserLand Software and
initially implemented in their Frontier product.