Please enable JavaScript.
Coggle requires JavaScript to display documents.
SOAP and REST (Simple Object Access Protocol (SOAP) (protocol (lightweight…
SOAP and REST
Simple Object Access Protocol (SOAP)
messaging framework
design
to be independent
other implementation specific semantics
programming model
goals
simplicity
extensibility
protocol
lightweight protocol
exchanging information
distributed environment
no data storage
each nodes contain information
each clients are equal and have equal rights
decentralized environment
different servers are connected to each other
no central storage
specification for exchanging structured information
for web services in computer networks
technologies used
XML
extensible messaging framework
can be exchanged over a variety of underlying protocols
Application layer protocols
HTTP
SMTP
messages
specified as an XML Information
can be used using a variety of underlying protocols
framework
relationship between bindings and SOAP nodes
HTTP binding in SOAP
facilitate consistency in the specification of optional features
process model
assumes
SOAP message
originates at an initial
SOAP sender
and is sent to an ultimate
SOAP receiver
action based
purpose
extensibility
neutrality
independence
ACID Compliance
reduces anomalies
protects the integrity of a database
tight security
SOAP and REST Key Differences
Formats
REST
permits many different formats
XML
JSON
HTML
SOAP
only XML
Design
REST
architectural style
SOAP
protocol
Methods
REST
access resource
data-driven
exposes named resources
SOAP
perform operation
function-driven
exposes components of application logic as service
Security
REST
can only use the secure version of HTTPS
SSL
SOAP
WS-Security
more comprehensive than SSL
enterprise-level security
Resource Usage
REST
lightweight
SOAP
more overhead
Caching
REST
cacheable
SOAP
can't be cached
Handling Application's Payload
REST
coupled to a lesser degree
less complex
easier to make updates without blowing up the whole relationship
SOAP
very closely coupled with the server
strict communication contract
difficult to make changes or updates
Request
REST
using URL
SOAP
using XML
REpresentational State Transfer (REST)
resource based
architectural style
framework to create a solution
distributed hypermedia
extension of hyperlink
non-linear medium
intended to be accessed in a non-linear fashion
interlinked diverse types
video
audio
plain text
hyperlink
graphics
constraints
client-server
separation of concerns
allows components to evolve
client-stateless-server (css)
session is only for client
induces properties
scalability
reliability
visibility
client-cache-stateless-server style
require data within reponse
implicit cacheable or non-cacheable
explicit cacheable or non-cacheable
uniform interface between components
implementations are decoupled from the services they provide
SOAP and REST Similarities
web service
can request
can have a response
can be used in API
can use HTTP as the transporter