hw2
TRANSCRIPT
Execution Environments for Distributed Computing
Why Use "REST" Architecture for Web
Services
EEDC
343
30
Master in Computer Architecture, Networks and Systems - CANS
Homework number: 2Umit Cavus Buyuksahin
2
OUTLINEOUTLINE
Web Services
SOAP & REST
Rest the Best
Who's using Rest
Conclusion
3
WEB SERVICESWEB SERVICES
... called application services
... language-independent protocol
... all communication in XML
... SOAP - UDDI - WSDL
4
WEB SERVICESWEB SERVICES
How it works?
5
SOAP & RESTSOAP & REST
SOAP (Simple Object Access Protocol)... for communication between applications... a format for sending messages... platform-language independent ... based on XML
REST (Representational State Transfer)... architectural style... dereferencing the URL... point-to-point exchange of information... doesn't specify a particular XML vocabulary
6
SOAP & RESTSOAP & REST
Which is the best?
7
REST the BESTREST the BEST
REST emphasizes:
scalability of component interactions
generality of interfaces
independent deployment of components
reduce interaction latency
enforce security
encapsulate legacy systems
8
REST the BESTREST the BEST
REST is better than SOAP, in terms of:
simpler to develop
less reliance on tools
permitting different data formats
performance and scalability
standardized, generic operations
utilizing the existing web addressing
totally stateless operations
9
WHO's USING RESTWHO's USING REST
10
CONCLUSIONCONCLUSION
REST describes the current Web architecture
REST principles can be applied to XML Web Services
SOAP enjoys broad industry support, extensibility
However;
Classic SOAP has some limitations compared to REST