Enviar búsqueda
Cargar
REST Design Patterns for SOA
•
0 recomendaciones
•
632 vistas
Título mejorado por IA
SOA Symposium
Seguir
Tecnología
Denunciar
Compartir
Denunciar
Compartir
1 de 23
Descargar ahora
Descargar para leer sin conexión
Recomendados
ESB Concepts
ESB Concepts
Tarandeep Sawhney
ESB and SOA
ESB and SOA
WSO2
Overview of SOA and the role of ESB / OSB
Overview of SOA and the role of ESB / OSB
Nahser Bakht
Why Enterprise Service Bus (ESB)
Why Enterprise Service Bus (ESB)
VTR Ravi Kumar
Overview of ESB at Azilen Tech Meetup
Overview of ESB at Azilen Tech Meetup
Azilen Technologies Pvt. Ltd.
Move up to POWER7 and IBM i 7, IBM Power Event
Move up to POWER7 and IBM i 7, IBM Power Event
IBM Danmark
Ibm connect 2014 recap asean perspective
Ibm connect 2014 recap asean perspective
Joseph George
SOA & ESB Presentation
SOA & ESB Presentation
erichleipold
Recomendados
ESB Concepts
ESB Concepts
Tarandeep Sawhney
ESB and SOA
ESB and SOA
WSO2
Overview of SOA and the role of ESB / OSB
Overview of SOA and the role of ESB / OSB
Nahser Bakht
Why Enterprise Service Bus (ESB)
Why Enterprise Service Bus (ESB)
VTR Ravi Kumar
Overview of ESB at Azilen Tech Meetup
Overview of ESB at Azilen Tech Meetup
Azilen Technologies Pvt. Ltd.
Move up to POWER7 and IBM i 7, IBM Power Event
Move up to POWER7 and IBM i 7, IBM Power Event
IBM Danmark
Ibm connect 2014 recap asean perspective
Ibm connect 2014 recap asean perspective
Joseph George
SOA & ESB Presentation
SOA & ESB Presentation
erichleipold
Connect 2017 - Melhores Momentos
Connect 2017 - Melhores Momentos
George Araujo
ESB Overview
ESB Overview
Bahaa Farouk
Introduction to Enterprise Service Bus
Introduction to Enterprise Service Bus
Mahmoud Ezzat
Visionet’S Capabilities & Offerings
Visionet’S Capabilities & Offerings
martinvisionet
Introduction to Enterprise Service Bus
Introduction to Enterprise Service Bus
Folio3 Software
SOA Governance and WebSphere Service Registry and Repository
SOA Governance and WebSphere Service Registry and Repository
IBM Sverige
Comment exploiter les solutions d'intégration entre applications Cloud et "on...
Comment exploiter les solutions d'intégration entre applications Cloud et "on...
Marc Jouve
SAP and IBM I
SAP and IBM I
IBM I community Israel
Enterprise Service Bus
Enterprise Service Bus
Hamed Hatami
ESB Presentation
ESB Presentation
F K
Enterprise service bus(esb)
Enterprise service bus(esb)
prksh89
Enterprise service bus part 1
Enterprise service bus part 1
Return on Intelligence
Enterprise Service Bus
Enterprise Service Bus
Return on Intelligence
Tactics Esb Implementation
Tactics Esb Implementation
Murali Manohar
New Ways To Engage With Tiempo 2011
New Ways To Engage With Tiempo 2011
Tiempo Development
WebServices and Workflow technologies
WebServices and Workflow technologies
Nitin Pande
Lotus® Symphony™ 3: One Million Reasons to Give it a try
Lotus® Symphony™ 3: One Million Reasons to Give it a try
Don Harbison
IBM Portal Web intro
IBM Portal Web intro
danisman
APIs Inside Enterprise - SOA Displacement?
APIs Inside Enterprise - SOA Displacement?
Apigee | Google Cloud
Dharmes Mistry Tony De Bree S O A Business Persp V1a
Dharmes Mistry Tony De Bree S O A Business Persp V1a
SOA Symposium
Andre Tost Service Models Java
Andre Tost Service Models Java
SOA Symposium
David Booth R D F & S O A
David Booth R D F & S O A
SOA Symposium
Más contenido relacionado
La actualidad más candente
Connect 2017 - Melhores Momentos
Connect 2017 - Melhores Momentos
George Araujo
ESB Overview
ESB Overview
Bahaa Farouk
Introduction to Enterprise Service Bus
Introduction to Enterprise Service Bus
Mahmoud Ezzat
Visionet’S Capabilities & Offerings
Visionet’S Capabilities & Offerings
martinvisionet
Introduction to Enterprise Service Bus
Introduction to Enterprise Service Bus
Folio3 Software
SOA Governance and WebSphere Service Registry and Repository
SOA Governance and WebSphere Service Registry and Repository
IBM Sverige
Comment exploiter les solutions d'intégration entre applications Cloud et "on...
Comment exploiter les solutions d'intégration entre applications Cloud et "on...
Marc Jouve
SAP and IBM I
SAP and IBM I
IBM I community Israel
Enterprise Service Bus
Enterprise Service Bus
Hamed Hatami
ESB Presentation
ESB Presentation
F K
Enterprise service bus(esb)
Enterprise service bus(esb)
prksh89
Enterprise service bus part 1
Enterprise service bus part 1
Return on Intelligence
Enterprise Service Bus
Enterprise Service Bus
Return on Intelligence
Tactics Esb Implementation
Tactics Esb Implementation
Murali Manohar
New Ways To Engage With Tiempo 2011
New Ways To Engage With Tiempo 2011
Tiempo Development
WebServices and Workflow technologies
WebServices and Workflow technologies
Nitin Pande
Lotus® Symphony™ 3: One Million Reasons to Give it a try
Lotus® Symphony™ 3: One Million Reasons to Give it a try
Don Harbison
IBM Portal Web intro
IBM Portal Web intro
danisman
APIs Inside Enterprise - SOA Displacement?
APIs Inside Enterprise - SOA Displacement?
Apigee | Google Cloud
La actualidad más candente
(19)
Connect 2017 - Melhores Momentos
Connect 2017 - Melhores Momentos
ESB Overview
ESB Overview
Introduction to Enterprise Service Bus
Introduction to Enterprise Service Bus
Visionet’S Capabilities & Offerings
Visionet’S Capabilities & Offerings
Introduction to Enterprise Service Bus
Introduction to Enterprise Service Bus
SOA Governance and WebSphere Service Registry and Repository
SOA Governance and WebSphere Service Registry and Repository
Comment exploiter les solutions d'intégration entre applications Cloud et "on...
Comment exploiter les solutions d'intégration entre applications Cloud et "on...
SAP and IBM I
SAP and IBM I
Enterprise Service Bus
Enterprise Service Bus
ESB Presentation
ESB Presentation
Enterprise service bus(esb)
Enterprise service bus(esb)
Enterprise service bus part 1
Enterprise service bus part 1
Enterprise Service Bus
Enterprise Service Bus
Tactics Esb Implementation
Tactics Esb Implementation
New Ways To Engage With Tiempo 2011
New Ways To Engage With Tiempo 2011
WebServices and Workflow technologies
WebServices and Workflow technologies
Lotus® Symphony™ 3: One Million Reasons to Give it a try
Lotus® Symphony™ 3: One Million Reasons to Give it a try
IBM Portal Web intro
IBM Portal Web intro
APIs Inside Enterprise - SOA Displacement?
APIs Inside Enterprise - SOA Displacement?
Destacado
Dharmes Mistry Tony De Bree S O A Business Persp V1a
Dharmes Mistry Tony De Bree S O A Business Persp V1a
SOA Symposium
Andre Tost Service Models Java
Andre Tost Service Models Java
SOA Symposium
David Booth R D F & S O A
David Booth R D F & S O A
SOA Symposium
Ian Robinson Testable Foundations
Ian Robinson Testable Foundations
SOA Symposium
Mark Little R E S Tand W S Star
Mark Little R E S Tand W S Star
SOA Symposium
Chris Riley Design Patterns For Web Service Versioning
Chris Riley Design Patterns For Web Service Versioning
SOA Symposium
Mohamad Afshar Moving Beyond Project Level S O A V1
Mohamad Afshar Moving Beyond Project Level S O A V1
SOA Symposium
Anish Karmakar S C A
Anish Karmakar S C A
SOA Symposium
Paul Butterworth Policy Based Approach
Paul Butterworth Policy Based Approach
SOA Symposium
Robert Schneider 10 Strategies
Robert Schneider 10 Strategies
SOA Symposium
Destacado
(10)
Dharmes Mistry Tony De Bree S O A Business Persp V1a
Dharmes Mistry Tony De Bree S O A Business Persp V1a
Andre Tost Service Models Java
Andre Tost Service Models Java
David Booth R D F & S O A
David Booth R D F & S O A
Ian Robinson Testable Foundations
Ian Robinson Testable Foundations
Mark Little R E S Tand W S Star
Mark Little R E S Tand W S Star
Chris Riley Design Patterns For Web Service Versioning
Chris Riley Design Patterns For Web Service Versioning
Mohamad Afshar Moving Beyond Project Level S O A V1
Mohamad Afshar Moving Beyond Project Level S O A V1
Anish Karmakar S C A
Anish Karmakar S C A
Paul Butterworth Policy Based Approach
Paul Butterworth Policy Based Approach
Robert Schneider 10 Strategies
Robert Schneider 10 Strategies
Similar a REST Design Patterns for SOA
Cloud adoption patterns
Cloud adoption patterns
Kyle Brown
Cloud adoption patterns April 11 2016
Cloud adoption patterns April 11 2016
Kyle Brown
USolutions - SOA and the Cloud
USolutions - SOA and the Cloud
usolutions
Mule Integration Simplified
Mule Integration Simplified
Bui Kiet
Differentiating between web APIs, SOA, & integration…and why it matters
Differentiating between web APIs, SOA, & integration…and why it matters
Kim Clark
IBM - Developing portlets using Script portlet in WP 8001
IBM - Developing portlets using Script portlet in WP 8001
Vinayak Tavargeri
Umit Yalcinalp Enterprise Mashupsfor S O A
Umit Yalcinalp Enterprise Mashupsfor S O A
SOA Symposium
IBM Z for the Digital Enterprise 2018 - Offering API channel to application a...
IBM Z for the Digital Enterprise 2018 - Offering API channel to application a...
DevOps for Enterprise Systems
Introduction to WebSphere Message Broker
Introduction to WebSphere Message Broker
Ant Phillips
Cloud Computing at UTM Shillong
Cloud Computing at UTM Shillong
Capgemini
Mule ESB - Integration Simplified
Mule ESB - Integration Simplified
Rich Software
IBM Z for the Digital Enterprise - Zowe overview
IBM Z for the Digital Enterprise - Zowe overview
DevOps for Enterprise Systems
A Flow Based Approach for End to End Mashups
A Flow Based Approach for End to End Mashups
raniakhalaf
Designing a Language and System for REST-oriented service composition,as a se...
Designing a Language and System for REST-oriented service composition,as a se...
raniakhalaf
Why ESB is wrong approach for cloud integration
Why ESB is wrong approach for cloud integration
Doug Lopp
EclipseCon 2013 Learn and share about integrations using Eclipse Lyo, OSLC an...
EclipseCon 2013 Learn and share about integrations using Eclipse Lyo, OSLC an...
Steve Speicher
ESB and Mule ESB solution
ESB and Mule ESB solution
Swati Bansal
Effective Application Development with WebSphere Message Broker
Effective Application Development with WebSphere Message Broker
Ant Phillips
The Three Stages of Cloud Adoption - RightScale Compute 2013
The Three Stages of Cloud Adoption - RightScale Compute 2013
RightScale
Simplified Web2.0 application development with Project Zero
Simplified Web2.0 application development with Project Zero
Shawn Zhu
Similar a REST Design Patterns for SOA
(20)
Cloud adoption patterns
Cloud adoption patterns
Cloud adoption patterns April 11 2016
Cloud adoption patterns April 11 2016
USolutions - SOA and the Cloud
USolutions - SOA and the Cloud
Mule Integration Simplified
Mule Integration Simplified
Differentiating between web APIs, SOA, & integration…and why it matters
Differentiating between web APIs, SOA, & integration…and why it matters
IBM - Developing portlets using Script portlet in WP 8001
IBM - Developing portlets using Script portlet in WP 8001
Umit Yalcinalp Enterprise Mashupsfor S O A
Umit Yalcinalp Enterprise Mashupsfor S O A
IBM Z for the Digital Enterprise 2018 - Offering API channel to application a...
IBM Z for the Digital Enterprise 2018 - Offering API channel to application a...
Introduction to WebSphere Message Broker
Introduction to WebSphere Message Broker
Cloud Computing at UTM Shillong
Cloud Computing at UTM Shillong
Mule ESB - Integration Simplified
Mule ESB - Integration Simplified
IBM Z for the Digital Enterprise - Zowe overview
IBM Z for the Digital Enterprise - Zowe overview
A Flow Based Approach for End to End Mashups
A Flow Based Approach for End to End Mashups
Designing a Language and System for REST-oriented service composition,as a se...
Designing a Language and System for REST-oriented service composition,as a se...
Why ESB is wrong approach for cloud integration
Why ESB is wrong approach for cloud integration
EclipseCon 2013 Learn and share about integrations using Eclipse Lyo, OSLC an...
EclipseCon 2013 Learn and share about integrations using Eclipse Lyo, OSLC an...
ESB and Mule ESB solution
ESB and Mule ESB solution
Effective Application Development with WebSphere Message Broker
Effective Application Development with WebSphere Message Broker
The Three Stages of Cloud Adoption - RightScale Compute 2013
The Three Stages of Cloud Adoption - RightScale Compute 2013
Simplified Web2.0 application development with Project Zero
Simplified Web2.0 application development with Project Zero
Más de SOA Symposium
Sven Hakan Olsson Composability Index V2
Sven Hakan Olsson Composability Index V2
SOA Symposium
Thomas Erl Introducing S O A Design Patterns
Thomas Erl Introducing S O A Design Patterns
SOA Symposium
Radovan Janecek Avoiding S O A Pitfalls
Radovan Janecek Avoiding S O A Pitfalls
SOA Symposium
Natasja Paulssen S A P M D M And E S O A At Philips
Natasja Paulssen S A P M D M And E S O A At Philips
SOA Symposium
Anthony Carrato S O A Business Architecture
Anthony Carrato S O A Business Architecture
SOA Symposium
David Chappel S O A Grid
David Chappel S O A Grid
SOA Symposium
Johan Kumps Federal E S B
Johan Kumps Federal E S B
SOA Symposium
Laurent Tarin B P M Ilog
Laurent Tarin B P M Ilog
SOA Symposium
Jim Webber Guerrilla S O A With Web Services
Jim Webber Guerrilla S O A With Web Services
SOA Symposium
Robert Schneider What Every Developer
Robert Schneider What Every Developer
SOA Symposium
Thomas Rischbeck Real Life E S B
Thomas Rischbeck Real Life E S B
SOA Symposium
Stefan Pappe Making S O A Operational
Stefan Pappe Making S O A Operational
SOA Symposium
Paul Brown Org Man Issues
Paul Brown Org Man Issues
SOA Symposium
Arnaud Simon Flight Data Processing
Arnaud Simon Flight Data Processing
SOA Symposium
Mark Little Web Services And Transactions
Mark Little Web Services And Transactions
SOA Symposium
S Ven Hakan Olsson Compos Index
S Ven Hakan Olsson Compos Index
SOA Symposium
Art Ligthart Service Identification Techniques
Art Ligthart Service Identification Techniques
SOA Symposium
Paul C Brown S O A Governance
Paul C Brown S O A Governance
SOA Symposium
Brian Loesgen An Early Look At Oslo
Brian Loesgen An Early Look At Oslo
SOA Symposium
Chris Riley S O A Modeling
Chris Riley S O A Modeling
SOA Symposium
Más de SOA Symposium
(20)
Sven Hakan Olsson Composability Index V2
Sven Hakan Olsson Composability Index V2
Thomas Erl Introducing S O A Design Patterns
Thomas Erl Introducing S O A Design Patterns
Radovan Janecek Avoiding S O A Pitfalls
Radovan Janecek Avoiding S O A Pitfalls
Natasja Paulssen S A P M D M And E S O A At Philips
Natasja Paulssen S A P M D M And E S O A At Philips
Anthony Carrato S O A Business Architecture
Anthony Carrato S O A Business Architecture
David Chappel S O A Grid
David Chappel S O A Grid
Johan Kumps Federal E S B
Johan Kumps Federal E S B
Laurent Tarin B P M Ilog
Laurent Tarin B P M Ilog
Jim Webber Guerrilla S O A With Web Services
Jim Webber Guerrilla S O A With Web Services
Robert Schneider What Every Developer
Robert Schneider What Every Developer
Thomas Rischbeck Real Life E S B
Thomas Rischbeck Real Life E S B
Stefan Pappe Making S O A Operational
Stefan Pappe Making S O A Operational
Paul Brown Org Man Issues
Paul Brown Org Man Issues
Arnaud Simon Flight Data Processing
Arnaud Simon Flight Data Processing
Mark Little Web Services And Transactions
Mark Little Web Services And Transactions
S Ven Hakan Olsson Compos Index
S Ven Hakan Olsson Compos Index
Art Ligthart Service Identification Techniques
Art Ligthart Service Identification Techniques
Paul C Brown S O A Governance
Paul C Brown S O A Governance
Brian Loesgen An Early Look At Oslo
Brian Loesgen An Early Look At Oslo
Chris Riley S O A Modeling
Chris Riley S O A Modeling
Último
How to Effectively Monitor SD-WAN and SASE Environments with ThousandEyes
How to Effectively Monitor SD-WAN and SASE Environments with ThousandEyes
ThousandEyes
Transcript: New from BookNet Canada for 2024: BNC SalesData and LibraryData -...
Transcript: New from BookNet Canada for 2024: BNC SalesData and LibraryData -...
BookNet Canada
The State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptx
LoriGlavin3
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
LoriGlavin3
Genislab builds better products and faster go-to-market with Lean project man...
Genislab builds better products and faster go-to-market with Lean project man...
Farhan Tariq
Arizona Broadband Policy Past, Present, and Future Presentation 3/25/24
Arizona Broadband Policy Past, Present, and Future Presentation 3/25/24
Mark Goldstein
Data governance with Unity Catalog Presentation
Data governance with Unity Catalog Presentation
Knoldus Inc.
2024 April Patch Tuesday
2024 April Patch Tuesday
Ivanti
Long journey of Ruby standard library at RubyConf AU 2024
Long journey of Ruby standard library at RubyConf AU 2024
Hiroshi SHIBATA
Potential of AI (Generative AI) in Business: Learnings and Insights
Potential of AI (Generative AI) in Business: Learnings and Insights
Ravi Sanghani
All These Sophisticated Attacks, Can We Really Detect Them - PDF
All These Sophisticated Attacks, Can We Really Detect Them - PDF
Michael Gough
QCon London: Mastering long-running processes in modern architectures
QCon London: Mastering long-running processes in modern architectures
Bernd Ruecker
Landscape Catalogue 2024 Australia-1.pdf
Landscape Catalogue 2024 Australia-1.pdf
Aarwolf Industries LLC
[Webinar] SpiraTest - Setting New Standards in Quality Assurance
[Webinar] SpiraTest - Setting New Standards in Quality Assurance
Inflectra
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
LoriGlavin3
Glenn Lazarus- Why Your Observability Strategy Needs Security Observability
Glenn Lazarus- Why Your Observability Strategy Needs Security Observability
itnewsafrica
Scale your database traffic with Read & Write split using MySQL Router
Scale your database traffic with Read & Write split using MySQL Router
Mydbops
Connecting the Dots for Information Discovery.pdf
Connecting the Dots for Information Discovery.pdf
Neo4j
MuleSoft Online Meetup Group - B2B Crash Course: Release SparkNotes
MuleSoft Online Meetup Group - B2B Crash Course: Release SparkNotes
Manik S Magar
A Glance At The Java Performance Toolbox
A Glance At The Java Performance Toolbox
Ana-Maria Mihalceanu
Último
(20)
How to Effectively Monitor SD-WAN and SASE Environments with ThousandEyes
How to Effectively Monitor SD-WAN and SASE Environments with ThousandEyes
Transcript: New from BookNet Canada for 2024: BNC SalesData and LibraryData -...
Transcript: New from BookNet Canada for 2024: BNC SalesData and LibraryData -...
The State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
Genislab builds better products and faster go-to-market with Lean project man...
Genislab builds better products and faster go-to-market with Lean project man...
Arizona Broadband Policy Past, Present, and Future Presentation 3/25/24
Arizona Broadband Policy Past, Present, and Future Presentation 3/25/24
Data governance with Unity Catalog Presentation
Data governance with Unity Catalog Presentation
2024 April Patch Tuesday
2024 April Patch Tuesday
Long journey of Ruby standard library at RubyConf AU 2024
Long journey of Ruby standard library at RubyConf AU 2024
Potential of AI (Generative AI) in Business: Learnings and Insights
Potential of AI (Generative AI) in Business: Learnings and Insights
All These Sophisticated Attacks, Can We Really Detect Them - PDF
All These Sophisticated Attacks, Can We Really Detect Them - PDF
QCon London: Mastering long-running processes in modern architectures
QCon London: Mastering long-running processes in modern architectures
Landscape Catalogue 2024 Australia-1.pdf
Landscape Catalogue 2024 Australia-1.pdf
[Webinar] SpiraTest - Setting New Standards in Quality Assurance
[Webinar] SpiraTest - Setting New Standards in Quality Assurance
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Glenn Lazarus- Why Your Observability Strategy Needs Security Observability
Glenn Lazarus- Why Your Observability Strategy Needs Security Observability
Scale your database traffic with Read & Write split using MySQL Router
Scale your database traffic with Read & Write split using MySQL Router
Connecting the Dots for Information Discovery.pdf
Connecting the Dots for Information Discovery.pdf
MuleSoft Online Meetup Group - B2B Crash Course: Release SparkNotes
MuleSoft Online Meetup Group - B2B Crash Course: Release SparkNotes
A Glance At The Java Performance Toolbox
A Glance At The Java Performance Toolbox
REST Design Patterns for SOA
1.
This Presentation Courtesy
of the International SOA Symposium October 7-8, 2008 Amsterdam Arena www.soasymposium.com info@soasymposium.com Founding Sponsors Platinum Sponsors Gold Sponsors Silver Sponsors IBM REST Design Patterns for SOA Raj Balasubramanian SOA Advanced Technology IBM Software Group raj_balasubramanian@us.ibm.com 09/15/08 2 © 2008 IBM Corporation 1
2.
IBM Agenda
Introduction Context Patterns Future work Q&A 3 09/15/08 © 2008 IBM Corporation IBM Introduction Customer facing consultant in IBM Software Group Experience with J2EE, Portal, SOA and recently Web 2.0 style applications in customer projects Interests in OWL and semantics, functional/logic programming for the web Built service providers on few different projects using the REST style, for consumption from Portal and other dynamic web apps 4 09/15/08 © 2008 IBM Corporation 2
3.
IBM Context - Timeline
Started working on a Portal/UI chapter for upcoming SOA with Java book Wrote a paper for my Masters Report on REST as an implementation style for a traditional SOA style system Started working on a REST chapter for the same book – SOA with Java 5 09/15/08 © 2008 IBM Corporation IBM Context - Timeline Approached by Thomas Erl to review SOA Design Patterns book As part of review suggested we look at few REST-inspired patterns that are unique from the rest (no pun) Had a short time frame to draft the initial list of patterns. Leveraged work from past to look at some key contributions REST could provide 6 09/15/08 © 2008 IBM Corporation 3
4.
IBM Context
Challenges – Keep these patterns at the same level as the other patterns in the book (SOA Design Patterns) – Introduce the patterns with no real orientation to REST, since the book assumed background knowledge on WS/SOAP/HTTP etc. – Time frame 7 09/15/08 © 2008 IBM Corporation IBM Context Thanks to – Thomas Erl – Jim Webber – Kevin Davis – Clemens Utschig 8 09/15/08 © 2008 IBM Corporation 4
5.
IBM Context
Disclaimer – This is not SOAP/WS* vs HTTP/REST – This is about REST as a design and realization paradigm for services – Strived to be unbiased by the politics 9 09/15/08 © 2008 IBM Corporation IBM Context Concept of a resource and RESTful services – Underpinnings of REST (as established by Roy T.Fielding’s thesis) and HTTP architecture form the basis of the following 5 basic patterns First batch of REST-inspired patterns More to come over time 10 09/15/08 © 2008 IBM Corporation 5
6.
IBM Context 11
09/15/08 © 2008 IBM Corporation IBM Patterns Uniform Interface – How can services share a common, standardized contract? Entity Linking – How can services maintain and expose the inherent linkage between business entities? Transport Caching – How can some of the temporal activity-specific state data be efficiently persisted? 12 09/15/08 © 2008 IBM Corporation 6
7.
IBM Patterns
Layered Redirect – How can a service be moved without impacting its consumers? Alternative Format – How can services exchange data based on less common or non-standard formats? 13 09/15/08 © 2008 IBM Corporation IBM Patterns Uniform Interface – How can services share a common, standardized contract? 14 09/15/08 © 2008 IBM Corporation 7
8.
IBM Pattern – Uniform
Interface Problem Custom contract design can be burdensome and risky when the contract content is subject to change – Designing customized service contracts that contain validation logic can lead to a variety of challenges: • Developers may be required to learn new technology languages. • The overall development effort of services increases due to the extra stage of having to custom build the contract content. • The contract design and validation logic can become outdated or can be subject to change, thereby risking dependencies formed on the contract by service consumers. • Furthermore, once changes to already-implemented service contracts are made, versioning responsibilities enter the picture, thereby increasing the governance burden of services. 15 09/15/08 © 2008 IBM Corporation IBM Pattern – Uniform Interface Solution A simple and highly generic contract is established and shared by a collection of services, thereby placing the design emphasis on location and structure of the information exchange – An existing, pre-defined, and generic service contract is used by all services. This simplifies the overall service inventory architecture and alleviates service designers from having to create individual contracts for services. It further shifts the customization to the data being passed to and from the Uniform Contract. 16 09/15/08 © 2008 IBM Corporation 8
9.
IBM Pattern – Uniform
Interface Sample 17 09/15/08 © 2008 IBM Corporation IBM Pattern – Uniform Interface Application The most common implementation of this pattern is existing practices around REST pattern that enables services to share the common HTTP method contract provided by the Web server – The primary application option for this pattern is HTTP method interface provided by all Web servers. Using this generic and prevalent contract, HTTP listeners can receive messages containing one of a number of pre- specified method verbs, such as GET, PUT, POST, DELETE, and HEAD. – The notion of Uniform Contract is a core tenet of the REST architectural style and therefore, when applying this pattern using REST, services must support some or all of the possible HTTP methods: – GET method – performs a read-only function that requires the service to be in the same state after the function is completed – PUT method – creates new data or data records within the service using the content provided in the HTTP Body field – HEAD method – carries out an inquiry about a given service without providing the entire response data – DELETE method – removes a specific body of data – POST method – can be used to selectively modify or create new data records – NOTE: For the traditional web service developer looking to use a single canonical WSDL to enforce this Uniform Contract pattern (by defining key service operations and using a generic schema for message type), the application of this pattern to web services is not appropriate. Since applying the Uniform Contract doesn’t leverage the intended richness of web services platform and related technology. The best use case of application of this pattern is by applying the REST design principles using HTTP. HTTP provides a global understanding and accepted standardization around the use of the uniform contract as enforced by the HTTP specification. 18 09/15/08 © 2008 IBM Corporation 9
10.
IBM Pattern – Uniform
Interface Impacts Validation logic that is commonly located in the contract layer must now be moved into the core service logic, and an absence of customized contract content introduces a reliance on supplementary human-readable content in order to discover and understand available services – Due to the simplicity of the multi-service contract established by this pattern, the richness of defining custom capabilities that semantically define related business tasks as desired by some service developers is lost. Because the single interface established by Uniform Contract is rigid, it can lead to • creative use of service definitions - by allocating service functionality to inappropriate operations • extensions of intended service operations – by creating variants of service operations from the Uniform Contract (as illustrated by the invention of new verbs in the WebDAV protocol) • both of which might undermine the goals of this Uniform Contract pattern. 19 09/15/08 © 2008 IBM Corporation IBM Patterns Entity Linking – How can services maintain and expose the inherent linkage between business entities? 20 09/15/08 © 2008 IBM Corporation 10
11.
IBM Pattern – Entity
Linking Problem Business entities are naturally inter-related, yet entity-centric services are commonly designed autonomously with no indication of these relationships – In any business environment there are entities that represent the primary and secondary artifacts involved in carrying out the business functions. These business entities can have numerous relationships with each other, many of which may even be dependencies. Some of these relations are physical in nature; some are implicit, while others may even be abstract. Understanding these relationships provides a useful insight as to the inner workings of an organization. – However, common service analysis and design approaches result in the delivery of services that are implemented independently with little to no indication of cross- entity relationships communicated to consumers. This can inhibit the consumer designers’ understanding of the business entity relationships 21 09/15/08 © 2008 IBM Corporation IBM Pattern – Entity Linking Solution Relationships between services are expressed via the association between entity-related data sets – The relationship between business entities is expressed through the service contract or by inter-linking data sets and making these data-level relationships the basis of service-consumer data exchanges . 22 09/15/08 © 2008 IBM Corporation 11
12.
IBM Pattern – Entity
Linking Application The most common implementation of this pattern is in the RESTful service that enables business entities to be linked at the information level using URIs in the form of anchor tags or XLink/XPointer in various content types. There are two approaches to explicitly associating entities together at the service level: – The service contract can provide specific capabilities with names that indicate entity relationships. – Uniform Contract can be applied, requiring that entity relationships be defined at the data level and within the corresponding HTTP response or request representation 23 09/15/08 © 2008 IBM Corporation IBM Pattern – Entity Linking Application The first approach is simply associated with how service capabilities are named. A Web service contract for a Customer service may expose an operation called “GetCustomerAccounts” to produce a listing of accounts for the given customer. In this case, the operation name itself communicates that the Customer and Accounts entities are related The second method relies on physically linking data sets at the level of representation in the request and response message together so that they can be accessed via the content of consumer request messages that express the same data entity relationships. In this case, Entity Linking is commonly applied by implementing a REST framework that positions a Uniform Contract via the standard HTTP method interface 24 09/15/08 © 2008 IBM Corporation 12
13.
IBM Pattern – Entity
Linking Application <xlink:type=”simple”xlink:href= "http://alleywoodcorp.com/services/customers/ab123"> Or <ahref=“http://alleywoodcorp.com/services/customers/ab123"> 25 09/15/08 © 2008 IBM Corporation IBM Pattern – Entity Linking Impacts Cross-business entity relationships tends to be more prone to change than the entities themselves, making established links also subject to change, which will impact service consumers – Although an extent of entity relationship information can be expressed through customized service contracts, it is almost never a complete representation as it pertains only to the functionality offered by the service at any given point in time. Furthermore, different naming conventions used to determine service and capability names may be too vague and not conducive to accurately describing the nature of these relationships. – When this pattern is applied to REST services, XML documents representing entity- centric data sets need to be physically linked. This can tightly bind the underling data architecture and future changes to these links can have significant impacts because consumers are required to couple to the manner in which these links are established. In essence, this design pattern can result in negative consumer-to-implementation coupling because it simulates the type of negative coupling that occurs when consumer programs are bound to service contracts that mirror underlying physical data models. – Furthermore, the primary benefit of navigability is lost when content types used to represent data sets have no standard means of accommodating links 26 09/15/08 © 2008 IBM Corporation 13
14.
IBM Patterns
Transport Caching – How can some of the temporal activity-specific state data be efficiently persisted? 27 09/15/08 © 2008 IBM Corporation IBM Pattern – Transport Caching Problem Services required to repeatedly exchange larger amounts of the same data can impose unnecessary runtime performance and bandwidth burden – Typical services are dynamic in nature, but there are instances when a subset of the information processed seldom changes. Repeatedly transmitting relatively static, state-specific data can be wasteful. – Then there are instances when the information is stable for a given period of time. In this case, the service is required to keep the data in memory while it perhaps waits for other processing to complete. This can be equally wasteful and can impede the service’s scalability 28 09/15/08 © 2008 IBM Corporation 14
15.
IBM Pattern – Transport
Caching Solution Services are designed to leverage built-in caching features provided by the transport communications framework in order to defer and persist some forms of state data – A transport communications framework with built-in caching features can be leveraged as a runtime state deferral mechanism. This allows the service to temporarily off-load static or idle state data until it needs to retrieve it at a later point. The result is that less data needs to be repeatedly transmitted and the service’s overall memory consumption is reduced . 29 09/15/08 © 2008 IBM Corporation IBM Pattern – Transport Caching Application Available caching features of an application protocol (most commonly HTTP) are incorporated into service and composition designs – Within contemporary service inventory architectures, this pattern is most commonly applied using the caching features provided by HTTP. – HTTP supplies a set of headers and associated rules that can be used to identify a cache, how (and how long) to cache state data and when it should be cached. By using these features, there are three common cache types that can be employed: • Gateway Caching – The service can using the centralized HTTP caching facility that is built into any Web server. This caching model is based on a reverse proxy that makes the decision as to whether to forward a request from the consumer to the service or to look it up in its cache. There are several variations of this caching model available in supplementary proxy products and appliances. • Intermediary Proxy Caching – Service consumers can use an intermediary facility based on a standard proxy server that provides a shared HTTP cache. Consumers will have to point to this proxy server before making any requests to the service itself. 30 09/15/08 © 2008 IBM Corporation 15
16.
IBM Pattern – Transport
Caching Application (contd.) • Client-side Caching – With this approach the cache resides in the presentation layer, usually as part of a rich application interface or Web browser. This option only pertains to services with which client-side programs interact directly. A common example is the use of REST services that help assemble presentation-centric mashups. – In addition to the caching options or strategies mentioned above, there are specific directives that the HTTP specification makes available to developers to implement caching, specifically leveraging HTTP headers, as follows: • The Response header can be used to dictate whether or not to cache a body of state data. In HTTP 1.1 it is represented by the Expires and Cache-Control header elements. • The Last-Modified response header and the If-Modified-Since request headers can be used to implement caching logic depending on when the state data was altered. The corresponding headers in HTTP 1.1 are the ETag response header and the If-None-Match request header. The decision to use a given header is made based on the benefits to the overall service architecture 31 09/15/08 © 2008 IBM Corporation IBM Pattern – Transport Caching Impacts Additional infrastructure may be required to effectively apply this pattern in high usage environments – The caching functionality provided by a transport communications framework can be convenient and efficient, but it may require additional infrastructure and associated caching configurations. Furthermore, there may be security implications to having data reside on the transport level, rather than behind the service contract as when State Repository or Stateful Services are applied . 32 09/15/08 © 2008 IBM Corporation 16
17.
IBM Patterns
Layered Redirect – How can a service be moved without impacting its consumers? 33 09/15/08 © 2008 IBM Corporation IBM Pattern – Layered Redirect Problem Various logistical circumstances may require a service to be physically relocated, thereby requiring configuration or code changes on the consumer end. There are numerous reasons as to why a service may need to be relocated: – IT departments may be subject to restructuring due to corporate acquisitions or company-wide re-organizations. – Infrastructure may need to be scaled requiring the introduction of new servers and the redistribution of previously deployed services. – New security requirements may demand that a service be isolated or relocated to a different enterprise domain 34 09/15/08 © 2008 IBM Corporation 17
18.
IBM Pattern – Layered
Redirect Solution Application and Transport-level redirect features are used to preserve consumer-to-service connectivity – There are two ways to address the problem: • Redirection at the Transport Protocol layer – This approach ensures the redirection occurs at the network transport protocol (TCP) layer and addressed by use of network devices. • Redirection at the Application Protocol layer– This approach ensures the redirection occurs at the application transport protocol (HTTP) layer and addressed by use of application proxies and intermediaries. – In addition to the above approaches, there can be two types of service relocation- • Transparent Relocation – This approach ensures that the consumer is unaware of the change and that all service interaction proceeds normally. • Relocation with Referrals – A mechanism residing at the service’s original location responds to consumer requests with an appropriate code indicating the new service location. 35 09/15/08 © 2008 IBM Corporation IBM Pattern – Layered Redirect Application Redirection logic placed at the original service location either transparently redirects consumer requests or responds to consumers with a notification indicating the new service location. This redirection can be applied at the transport protocol level or at the application protocol level – Transparent relocation is typically achieved by the application of Intermediate Routing together with specialized redirection logic or by using core networking services (such as DNS). This redirection can be implemented at the Transport or Application Protocol layer. At the transport protocol layer, network appliances are used. This can be applied to both HTTP based REST services as well as SOAP based web services. HTTP specification offers guidance on accomplishing the redirects as indicated below. This is leveraged fully in RESTful services. For SOAP based services, there are additional intermediaries in the form of middleware environments, such as the Enterprise Service Bus, to accomplish routing functionality – Implementing relocation by referral can also be achieved via Intermediate Routing logic, but is more commonly built at the application protocol layer. HTTP specification offers guidance on accomplishing the redirects as indicated below. This is leveraged fully in RESTful services. – The HTTP specification contains several provisions that address temporary move and permanent moves, primarily due to its origins in Web publishing. Some of the more relevant HTTP codes that are associated with the header fields in the HTTP response include: • 301 Moved Permanently • 302 Found • 303 See Other • 307 Temporary Redirect – The modified address or the older address of the service is specified in the Location field in the response header. Additional information can be provided in the response body. 36 09/15/08 © 2008 IBM Corporation 18
19.
IBM Pattern – Layered
Redirect Impacts Requires additional planning of resource design as well as possible impact to the intermediaries – proxies, network devices etc – When following the transparent relocation approach, it may be tempting to never update consumers because service interaction continues to occur as it always has. For anything that requires more than changes at the networking (DNS) level, this pattern can lead to the need for middleware or network appliances and can further compound governance efforts required to keep track of all of the old and updated locations that need to be continually maintained. – The relocation by referral method either requires that consumers undergo a change to incorporate the new service location or that they be designed to receive the response codes containing the relocation information. Either way, this will impact consumer programs that were not designed for this type of response. • Note: Due to the HTTP-centric nature of REST-based implementations, consumers of REST services may naturally contain the processing logic required to accept HTTP response codes . 37 09/15/08 © 2008 IBM Corporation IBM Patterns Alternative Format – How can services exchange data based on less common or non-standard formats? 38 09/15/08 © 2008 IBM Corporation 19
20.
IBM Pattern – Alternative
Format Problem Service consumers may have data exchange requirements based on non-XML formats – Service consumers can have diverse requirements, especially when they exist as alternative programs in mobile devices or on desktop applications. Whereas most consumers will tend to expect a standard XML representation, others may require different formats, such as binary-encoded images or portable data format (PDF) based data 39 09/15/08 © 2008 IBM Corporation IBM Pattern – Alternative Format Solution Services can be designed to exchange data in alternative representation formats, thereby accommodating special consumer requirements – Services are designed to support data exchange in multiple or alternative data formats. Either service contracts are extended to include additional capabilities with the functionality to receive and respond with messages containing different formats, or processing is added to transform a service’s natural data representation format to and from the consumer’s desired representation format . 40 09/15/08 © 2008 IBM Corporation 20
21.
IBM Pattern – Alternative
Format Application How this pattern is applied is dependent on the endpoint type of the service and technology required to support the desired data format . There are two common approaches for supporting Alternative Format in services: – Use an attachment technology to associate the alternatively formatted data with an XML message and configure the service to address the processing of these attached content formats. – Use any one of the supported content-types or custom representation, available natively to the application protocol (such as HTTP) and configure the service to address the processing of these different content formats. 41 09/15/08 © 2008 IBM Corporation IBM Pattern – Alternative Format Application (contd.) HTTP Mime-type example-For example, to represent XML the media- type value would be text/xml or application/xml, to represent HTML it is text/html, and the Adobe PDF format is application/pdf. When using HTTP functionality with a REST framework (such as Restlet etc.) of choice, the JSON (JavaScript Object Notation) format is also commonly supported. Hence a web application consuming this service from a browser can process this response with little overhead as these are just another JavaScript objects. For example, this simple XML fragment: ...would be represented in JSON as: <customers> {customers:{ customer:[ <customer> { name:”John Smith”, <name>John Smith</name> type:”Gold” } <type>Gold</type> ] </customer> } } </customers> 42 09/15/08 © 2008 IBM Corporation 21
22.
IBM Pattern – Alternative
Format Impacts This pattern can deviate from the goal of establishing Canonical Schema in a single representation format, across an enterprise – The primary impact is on the service implementation, since the additional logic to accept the various media-types and respond with unique media-types has to be addressed as part of the implementation. The impact on the consumer is that they have to perform additional calls to the service to inquire about the supported content as part of the content negotiation process . 43 09/15/08 © 2008 IBM Corporation IBM Patterns - Relations Entity Linking can support leverages leverages Alternative Format Uniform Layered Redirect leverages Contract leverages can facilitates leverages support Transport Caching used in combination with 44 09/15/08 © 2008 IBM Corporation 22
23.
IBM Thank You
09/15/08 45 © 2008 IBM Corporation 23
Descargar ahora