Chapter 3: Programming Web Services Service-Oriented Computing: Semantics, Processes, Agents – Munindar P. Singh and Michael N. Huhns, Wiley, 2005.

Slides:



Advertisements
Similar presentations
Give it a REST already Arnon Rotem-Gal-Oz VP R&D xsights
Advertisements

Representational State Transfer (REST) Paul Townend 8 th February 2007.
REST - Representational State Transfer
REST Vs. SOAP.
REST Introduction 吴海生 博克软件(杭州)有限公司.
Introduction to Web Services
Programming Web Services: RPC via SOAP and REST. 2Service-Oriented Computing RPC via SOAP A Web service is typically invoked by sending a SOAP message.
Chapter 10: Execution Models Service-Oriented Computing: Semantics, Processes, Agents – Munindar P. Singh and Michael N. Huhns, Wiley, 2005.
Database Architectures and the Web
Chapter 16: Multiagent Systems Service-Oriented Computing: Semantics, Processes, Agents – Munindar P. Singh and Michael N. Huhns, Wiley, 2005.
Message Queues COMP3017 Advanced Databases Dr Nicholas Gibbins –
Chapter 3 Database Architectures and the Web Pearson Education © 2009.
COMPARING DIFFERENT SOFTWARE INTEGRATION TECHNOLOGIES Author Jones Olaiya Ogunduyilemi (Internet & Software Technology)
Chapter 5: Principles of Service- Oriented Computing Service-Oriented Computing: Semantics, Processes, Agents – Munindar P. Singh and Michael N. Huhns,
Software Engineering and Middleware: a Roadmap by Wolfgang Emmerich Ebru Dincel Sahitya Gupta.
CS 415 N-Tier Application Development By Umair Ashraf July 6,2013 National University of Computer and Emerging Sciences Lecture # 9 Introduction to Web.
Web Services Michael Smith Alex Feldman. What is a Web Service? A Web service is a message-oriented software system designed to support inter-operable.
Slide 1 of 9 Presenting 24x7 Scheduler The art of computer automation Press PageDown key or click to advance.
Chapter 3 Database Architectures and the Web Pearson Education © 2009.
WORKFLOW IN MOBILE ENVIRONMENT. WHAT IS WORKFLOW ?  WORKFLOW IS A COLLECTION OF TASKS ORGANIZED TO ACCOMPLISH SOME BUSINESS PROCESS.  EXAMPLE: Patient.
Database Architectures and the Web
Chapter 5: Principles of Service- Oriented Computing Service-Oriented Computing: Semantics, Processes, Agents – Munindar P. Singh and Michael N. Huhns,
What is Architecture  Architecture is a subjective thing, a shared understanding of a system’s design by the expert developers on a project  In the.
Database Architectures and the Web Session 5
ITIS 1210 Introduction to Web-Based Information Systems Chapter 43 Shopping on the Internet.
Web Architecture & Services (2) Representational State Transfer (REST)
REST.  REST is an acronym standing for Representational State Transfer  A software architecture style for building scalable web services  Typically,
Client Server Technologies Middleware Technologies Ganesh Panchanathan Alex Verstak.
Chapter 1: Computing with Services Service-Oriented Computing: Semantics, Processes, Agents – Munindar P. Singh and Michael N. Huhns, Wiley, 2005.
9/5/2012ISC329 Isabelle Bichindaritz1 Web Database Environment.
Architectures of distributed systems Fundamental Models
1 Introduction to Middleware. 2 Outline What is middleware? Purpose and origin Why use it? What Middleware does? Technical details Middleware services.
Chapter 22: Building SOC Applications Service-Oriented Computing: Semantics, Processes, Agents – Munindar P. Singh and Michael N. Huhns, Wiley, 2005.
1 Welcome to CSC 301 Web Programming Charles Frank.
REST - Introduction Based on material from InfoQ.com (Stefan Tilkov) And slides from MindTouch.com (Steve Bjorg) 1.
Database Design – Lecture 18 Client/Server, Data Warehouse and E-Commerce Database Design.
Elmasri and Navathe, Fundamentals of Database Systems, Fourth Edition Copyright © 2004 Pearson Education, Inc. Slide 2-1 Data Models Data Model: A set.
1 Seminar on Service Oriented Architecture Principles of REST.
World Wide Web “WWW”, "Web" or "W3". World Wide Web “WWW”, "Web" or "W3"
1 WWW. 2 World Wide Web Major application protocol used on the Internet Simple interface Two concepts –Point –Click.
Advanced Web Technologies Lecture #4 By: Faraz Ahmed.
Representational State Transfer (REST). What is REST? Network Architectural style Overview: –Resources are defined and addressed –Transmits domain-specific.
RESTful Web Services What is RESTful?
Chapter 1: Computing with Services Service-Oriented Computing: Semantics, Processes, Agents – Munindar P. Singh and Michael N. Huhns, Wiley, 2005.
Data Communications and Networks Chapter 9 – Distributed Systems ICT-BVF8.1- Data Communications and Network Trainer: Dr. Abbes Sebihi.
REST By: Vishwanath Vineet.
Web Technologies Lecture 10 Web services. From W3C – A software system designed to support interoperable machine-to-machine interaction over a network.
E-commerce Architecture Ayşe Başar Bener. Client Server Architecture E-commerce is based on client/ server architecture –Client processes requesting service.
Representational State Transfer COMP6017 Topics on Web Services Dr Nicholas Gibbins –
REST API Design. Application API API = Application Programming Interface APIs expose functionality of an application or service that exists independently.
A service Oriented Architecture & Web Service Technology.
Service-Oriented Computing: Semantics, Processes, Agents
Database Architectures and the Web
REST- Representational State Transfer Enn Õunapuu
Database Architectures and the Web
Representational State Transfer
Ashish Pandit IT Architect, Middleware & Integration Services
Service-Oriented Computing: Semantics, Processes, Agents
Service-Oriented Computing: Semantics, Processes, Agents
Service-Oriented Computing: Semantics, Processes, Agents
Service-Oriented Computing: Semantics, Processes, Agents
Service-Oriented Computing: Semantics, Processes, Agents
Service-Oriented Computing: Semantics, Processes, Agents
Service-Oriented Computing: Semantics, Processes, Agents
Web Application Server 2001/3/27 Kang, Seungwoo. Web Application Server A class of middleware Speeding application development Strategic platform for.
Service-Oriented Computing: Semantics, Processes, Agents
RESTful Web Services.
REST på Microsoft-stacken
Service-Oriented Computing: Semantics, Processes, Agents
Presentation transcript:

Chapter 3: Programming Web Services Service-Oriented Computing: Semantics, Processes, Agents – Munindar P. Singh and Michael N. Huhns, Wiley, 2005

Chapter 32Service-Oriented Computing: Semantics, Processes, Agents - Munindar Singh and Michael Huhns Highlights of this Chapter Representational State Transfer (ReST or REST) Developing and Using Web Services Web Service Interoperability

Chapter 33Service-Oriented Computing: Semantics, Processes, Agents - Munindar Singh and Michael Huhns Representational State Transfer REST is an architectural style for networked systems that constrains the connector semantics (not the component semantics) The Web is a network of hyperlinked resources A resource is anything identified by a URI A Web application works as a state machine A client selecting a link is a state transition, resulting in receiving the next page (next state) of the application

Chapter 34Service-Oriented Computing: Semantics, Processes, Agents - Munindar Singh and Michael Huhns Characteristics of REST Client-Server Statelessness: requests cannot take advantage of stored contexts on a server Great for load balancing Caching: responses can be labeled as cacheable Uniform interface: URIs, hypermedia Layered components Focus on resources as opposed to methods: Read, construct, update a resource representation Well-suited to hypermedia applications

HTTP Verbs Popular verbs Get: query (no side effects) Post: update Put Delete In particular, can use Get and Post instead of much of SOAP Idempotent operations Multiple executions = one execution Challenge: the specification imposes requirements but with no way to judge compliance without understanding the designer’s intent Chapter 35Service-Oriented Computing: Semantics, Processes, Agents - Munindar Singh and Michael Huhns

Chapter 36Service-Oriented Computing: Semantics, Processes, Agents - Munindar Singh and Michael Huhns Software for Open Environments Tempting to simply lift current database and programming techniques for open environments Popular pitfall (blame the tools for it) Think of objects (get and set methods) ERROR: Too fine a granularity (see chapter 4) Invoke them as objects even though they are Web services Poor performance Tight coupling

Chapter 37Service-Oriented Computing: Semantics, Processes, Agents - Munindar Singh and Michael Huhns Suppose you want to sell cameras over the Web, debit a credit card, and guarantee next-day delivery Your application must update sales database debit the credit card send an order to the shipping department receive an OK from the shipping department for next-day delivery update an inventory database Problems: Some steps complete but not all Simple B2C Web Service Example

Chapter 38Service-Oriented Computing: Semantics, Processes, Agents - Munindar Singh and Michael Huhns “Traditional” B2C Problems What if the order is shipped, but the debit fails? What if the debit succeeds, but the order was never entered or shipped?

Chapter 39Service-Oriented Computing: Semantics, Processes, Agents - Munindar Singh and Michael Huhns Traditional Database Approach A traditional database approach works only for a closed environment: Transaction processing (TP) monitors (such as IBM’s CICS, Transarc’s Encina, BEA System’s Tuxedo) can ensure that all or none of the steps are completed, and that systems eventually reach a consistent state But what if the user’s modem is disconnected right after he clicks on OK? Did the order succeed? What if the line went dead before the acknowledgement arrives? Will the user order again? The TP monitor cannot get the user into a consistent state!

Chapter 310Service-Oriented Computing: Semantics, Processes, Agents - Munindar Singh and Michael Huhns Approach for Open Environment Server application could send about credit problems, or detect duplicate transactions Downloaded applet could synchronize with server after broken connection was restored, and recover transaction; applet could communicate using http, or directly with server objects via CORBA/IIOP or RMI If there are too many orders to process synchronously, they could be put in a message queue, managed by a Message Oriented Middleware server (which guarantees message delivery or failure notification), and customers would be notified by when the transaction is complete The server behaves like an agent!

Chapter 311Service-Oriented Computing: Semantics, Processes, Agents - Munindar Singh and Michael Huhns Requirements Cross-enterprise processes Autonomy (whim) Exception handling Revisions (necessity) How to deal with the above Conversations and long-lived transactions Contracts among parties involved

Chapter 312Service-Oriented Computing: Semantics, Processes, Agents - Munindar Singh and Michael Huhns Chapter 3 Summary Tools help with low-level details Agreeing on standards is more important than the standards themselves Should conceptualize interactions in a manner compatible with the Web architecture Can simplify from SOAP in many cases The above is a small point anyway Bigger challenges are in ensuring larger-scale interactions, ensuring integrity, handling exceptions, … Sophisticated programming models are emerging