The document describes a hypothetical scenario to understand REST and SOAP web services. A biologist wants to visualize chromosome sequences and asks a programmer to create an application. The programmer finds a web service providing genome sequences and looks up documentation on how to request sequences from the service. The programmer encodes logic into an application to retrieve and present the information. The biologist then uses the application, which sends requests to the service and presents the response to the biologist.
2. Hypothetical scenario to understand
REST and SOAP Web Services
A biologist wants a software application to visualize chromosome sequences
A. The biologist ask a programmer
B. The programmer creates an application
C. The biologist uses the application
A. The programmer creates an application
1. The programmer finds a web service providing genome sequences
2. The programmer looks for documentation about how to request sequences in this service
3. Programmer encodes logic to retrieve and present information into an application
B. The biologist uses the application
1. The biologist queries the application
2. The application sends a request to the service
3. The service provides a response to the application
4. The application present the information to the biologist
3. Web Services
How should I invoke you?
Documentation
Make a request
Results
Web server
Application
describes the methods and variables to query the service
1
2
3
4
2
Developer
4. REST Web Services
How should I invoke you?
Documentation
Make a request ( GET or POST)
Results (data + status)
Web server
Sometimes a WADL file is available in the server to describe
the service
1
2
3
4
2
WADLor
Informal
Description
Formal
Description
Application
Developer
5. SOAP Web Services
How should I invoke you?
Documentation (WSDL)
Make a SOAP request
Web server1
2
3
WSDL
Method / Parameters Data
4
3 4SOAP request SOAP response
and
Informal
Description
Formal
Description
Results (SOAP response)
Application
Developer