Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
Web Services Overview
Transcript of Web Services Overview
- use independent transport protocol (HTTP, SMTP...) Challenges - Client & provider not in the same processing environment - Unpredictable reliability & latency of network communication - Concurrency issues - Partial failure scenarios When to use SOA and WS? SOA is form of distributed system based on WS Use when: applications must operate over internet (speed & reliability not guaranteed) client & providers can't be deployed at once component run on different platform & vendor product to expose existing application Types SOAP WS REST WS exposes arbitrary set of operations manipulate web resources through uniform stateless operations formal machine processable description can be mapped to any languages WSDL SOAP messages request / response are both SOAP messages Architecture of SOAP WS provider- consumer- different platform / implementation language XML acts as intermediary WSDL Using Web Services One-Way Solicit / Response Notification <operation>
</operation> Give every "thing" a unique ID - URI Light Weight compare to SOAP ` Messages can be XML, JSON or others... Questions? The 5 REST Principles Described by Roy Fielding to explain the pervasiveness of WWW Realization that the same principles can be used to build Web Services Addressability Uniform Constrained Interface Use finite set of standard methods Representation Oriented Resources have multiple representations Stateless Communication No client session stored on the server HATEOAS - Hypermedia As The Engine Of Application State Link things together Services become linkable URI - http://test.com/rest/service Uses HTTP as application protocol GET PUT DELETE POST Familiarity - no need of IDL Interoperability-HTTP widely supported Scalability - cache, idempotent methods Content-type - notify client of format Address/Method/Content negotiation - allow for decoupled service Accept -client indicates preferred content Client state stored by client and sent as needed Scaling easier - fewer expensive replications in clustered environment Reference and aggregate additional data Engine of application state - response tells where to go next REST versus SOAP Ease of learning and development - specially client side Complex to learn, develop - additional software, stubs Use of existing Web infrastructure - HTTP Generic transport (HTTP, SPTP, JMS) Lacks Standards Standards & well defined protocol & rules Mature & established When to Use? SOAP REST Limited bandwidth Caching Guaranteed reliability Formal contracts Statefull operations Attachments Stateless Open for development SOAP versus REST