Hw2
Upcoming SlideShare
Loading in...5
×
 

Hw2

on

  • 305 views

 

Statistics

Views

Total Views
305
Views on SlideShare
305
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Hw2 Hw2 Presentation Transcript

  • Execution Environments for Distributed Computing Why Use "REST" Architecture for Web Services EEDC 34330 Master in Computer Architecture, Networks and Systems - CANS Homework number: 2 Umit Cavus Buyuksahin [email_address]
  • OUTLINE
    • Web Services
    • SOAP & REST
    • Rest the Best
    • Who's using Rest
    • Conclusion
  • WEB SERVICES
    • ... called application services
    • ... language-independent protocol
    • ... all communication in XML
    • ... SOAP - UDDI - WSDL
  • WEB SERVICES
    • How it works?
  • SOAP & 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
  • SOAP & REST
    • Which is the best?
  • REST the BEST
    • REST emphasizes:
      • scalability of component interactions
      • generality of interfaces
      • independent deployment of components
      • reduce interaction latency
      • enforce security
      • encapsulate legacy systems
  • REST 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
  • WHO's USING REST
  • CONCLUSION
    • 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