Soa Symposium Rest Style Soa Governance 2009 10 23 Bc
•Download as PPT, PDF•
0 likes•321 views
This document discusses governance considerations for REST-style service-oriented architectures (SOAs). It outlines how REST constraints impact technology, processes, and organization compared to traditional SOA governance models. Specifically, it focuses on how the uniform contract of REST requires governance of contract and media type definitions across services to ensure interoperability. New processes may also be needed for managing changes to the uniform contract. Overall, REST requires a shift to more centralized governance of contracts, media types and methods while still allowing flexibility for individual services.
Report
Share
Report
Share
![Overview ,[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Uunit 5-xml&web security
This document discusses metadata, security, transactions, and reliable messaging specifications for web services. It provides an overview of key specifications such as WSDL, WS-Security, WS-Transactions, and WS-Reliable Messaging that define standards for describing, securing, and coordinating web services and messages. The document also covers standards for integrating mobile devices into a service-oriented architecture.
Tulsa Tech Fest2008 Service Oriented Development With Windows Communication F...
The document discusses service oriented development with Windows Communication Foundation (WCF). It covers the evolution of service orientation including object-oriented programming, component-based development, and service-oriented architecture. It then discusses key concepts of WCF including contracts, bindings, and transports. Finally, it provides examples of how to configure services and endpoints in WCF.
Service Oriented Development With Windows Communication Foundation Tulsa Dnug
The document discusses key concepts in service-oriented development using Windows Communication Foundation (WCF). It defines terms like service, endpoint, binding, contract, and describes how they relate. It also covers messaging patterns, security, reliability, hosting and more WCF features.
Unit 3-SOA Technologies
This document discusses technologies for enabling service-oriented architectures (SOAs). It covers generic technologies like RESTful and SOAP web services. Platform-specific technologies for Java (JAX-WS) and .NET (.NET, WCF) are also discussed. Standards like XML, HTTP, SOAP, WSDL, and UDDI that web services are built on are explained. The roles of service providers, consumers and registries are defined. Enterprise service buses and their role in service integration are summarized. Finally, factors to consider in building a business case for SOA like stakeholders' objectives, benefits, cost savings, and return on investment are outlined.
Unit 2 -SOA design
This document discusses principles and processes for service-oriented architecture (SOA) design. It outlines four types of services - client, business process management, business application, and data services. It describes the SOA design process for an enterprise, including developing activity services from business applications, business process services using orchestration tools, and client and data services. The goals of SOA design are reusability, agility, and loose integration of services.
Introduction to Micro Services
This is a brief introduction to a new style of architecture also called as micro-service architectural style.
Web Service Oriented Architecture
There are two main types of distributed systems: request/response and message passing. Request/response systems focus on invoking operations and return values, while message passing focuses on constructing and dispatching messages without expecting a response. There are also two main architecture styles: object-oriented and service-oriented. Object-oriented styles involve communicating with object instances and have stateful communications, while service-oriented styles involve communicating with services through a standardized interface in a stateless manner. A shift is occurring from object-oriented to service-oriented architectures, as the latter allows for looser coupling and better scalability through messages. Web services can support both request/response and message passing systems.
Delivering Process-Driven, Dynamic Applications
The document discusses model-driven business process management (BPM) using template-driven approaches. It proposes using XML templates and the OASIS Content Assembly Mechanism (CAM) to [1] align business concepts with implementations, [2] generate documentation to communicate rules to stakeholders, and [3] enable agile information exchanges through reusable templates. CAM allows adding validation rules to templates extracted from XSDs to make exchanges more robust and interoperable compared to static schemas. The approach aims to make BPM more context-aware, self-adaptive, and able to flexibly support changing requirements.
Recommended
Uunit 5-xml&web security
This document discusses metadata, security, transactions, and reliable messaging specifications for web services. It provides an overview of key specifications such as WSDL, WS-Security, WS-Transactions, and WS-Reliable Messaging that define standards for describing, securing, and coordinating web services and messages. The document also covers standards for integrating mobile devices into a service-oriented architecture.
Tulsa Tech Fest2008 Service Oriented Development With Windows Communication F...
The document discusses service oriented development with Windows Communication Foundation (WCF). It covers the evolution of service orientation including object-oriented programming, component-based development, and service-oriented architecture. It then discusses key concepts of WCF including contracts, bindings, and transports. Finally, it provides examples of how to configure services and endpoints in WCF.
Service Oriented Development With Windows Communication Foundation Tulsa Dnug
The document discusses key concepts in service-oriented development using Windows Communication Foundation (WCF). It defines terms like service, endpoint, binding, contract, and describes how they relate. It also covers messaging patterns, security, reliability, hosting and more WCF features.
Unit 3-SOA Technologies
This document discusses technologies for enabling service-oriented architectures (SOAs). It covers generic technologies like RESTful and SOAP web services. Platform-specific technologies for Java (JAX-WS) and .NET (.NET, WCF) are also discussed. Standards like XML, HTTP, SOAP, WSDL, and UDDI that web services are built on are explained. The roles of service providers, consumers and registries are defined. Enterprise service buses and their role in service integration are summarized. Finally, factors to consider in building a business case for SOA like stakeholders' objectives, benefits, cost savings, and return on investment are outlined.
Unit 2 -SOA design
This document discusses principles and processes for service-oriented architecture (SOA) design. It outlines four types of services - client, business process management, business application, and data services. It describes the SOA design process for an enterprise, including developing activity services from business applications, business process services using orchestration tools, and client and data services. The goals of SOA design are reusability, agility, and loose integration of services.
Introduction to Micro Services
This is a brief introduction to a new style of architecture also called as micro-service architectural style.
Web Service Oriented Architecture
There are two main types of distributed systems: request/response and message passing. Request/response systems focus on invoking operations and return values, while message passing focuses on constructing and dispatching messages without expecting a response. There are also two main architecture styles: object-oriented and service-oriented. Object-oriented styles involve communicating with object instances and have stateful communications, while service-oriented styles involve communicating with services through a standardized interface in a stateless manner. A shift is occurring from object-oriented to service-oriented architectures, as the latter allows for looser coupling and better scalability through messages. Web services can support both request/response and message passing systems.
Delivering Process-Driven, Dynamic Applications
The document discusses model-driven business process management (BPM) using template-driven approaches. It proposes using XML templates and the OASIS Content Assembly Mechanism (CAM) to [1] align business concepts with implementations, [2] generate documentation to communicate rules to stakeholders, and [3] enable agile information exchanges through reusable templates. CAM allows adding validation rules to templates extracted from XSDs to make exchanges more robust and interoperable compared to static schemas. The approach aims to make BPM more context-aware, self-adaptive, and able to flexibly support changing requirements.
Japanese Child Care
This document outlines an agenda for presenting on childcare systems in Japan. It will introduce Japan, discuss the formal and informal childcare system including philosophy, age groups, teachers, who pays, and accessibility. It will then compare the similarities and differences between childcare systems and conclude the presentation.
Co branded collateral
This document discusses various partner co-branding and collateral opportunities between ForkFly and traditional media partners, including 30-second television spots, bus advertisements, billboards, distribution boxes, radio advertisements, banner ads on local news sites, web pop-ups, print ads, and branded merchandise for partners in cities such as Monroe, LA, Spokane, WA, Klamath Falls, OR, and others.
Podcasting Education
This document discusses the benefits of using podcasting in education. It notes that podcasting allows for flexibility and accessibility of content for students with different learning styles. While not all students may benefit equally from audio-based instruction, podcasts can be an effective supplement when designed based on an understanding of individual learning preferences. The document provides guidance on how to create podcasts using free, easy-to-use software and export them for playback on digital devices. It concludes that podcasting is a valuable educational tool when it caters to diverse student learning styles.
ForkFly for Media
ForkFly is a self-service platform that allows media partners to monetize digital advertising in new ways and engage advertisers and audiences through their mobile and web apps. It provides geo-targeted deals and incentives to local audiences while giving advertisers tools to build their brand and customer base. Advertisers pay monthly subscriptions for unlimited offers and analytics to understand customer behavior. Media partners can generate revenue through the subscriptions, daily deals programs, and banner ads on their sites.
SCrude Photography Demo
SCrude Photography is a photography business owned by Christopher Kidder that specializes in distorting imagery through unconventional techniques in a single shot. The business can be contacted at 323.839.7893 for photography services that manipulate images in unusual ways with each photo.
Geometry In The Real World
This document defines and describes basic geometric shapes and terms. It defines points, lines, planes, angles, perpendicular and parallel lines, triangles, polygons, quadrilaterals like squares, rectangles, trapezoids and parallelograms, circles, cylinders, spheres, ovals, and properties like concurrent lines and types of quadrilaterals like rhombuses. Key geometric concepts and their definitions are provided to establish common understanding of shape names and characteristics.
Quality of Consumer Experience in the Future Internet
Quality of Experience in the Future Internet era: NEM and the broadcaster\'s perspective. Future Internet Assembly, Stockholm, November 2009.
Soa Symposium Expressing Service Capabilities Uniformly 2009 10 14 Bc
The document discusses using a uniform contract to increase integration maturity in service-oriented architectures (SOAs). It proposes expressing service capabilities through resources to create a more abstract interface. The key steps to transform an existing service contract to a uniform contract are outlined, which include splitting nouns from verbs, identifying entity identifiers, and reusing uniform contract elements. Examples of transforming common service operations, like getting prices or making payments, into resource-based interfaces are provided. The benefits of a resource-based approach include enabling runtime discovery and flexible orchestration of services.
Service Oriented Architecture
The document discusses Service Oriented Architecture (SOA). It defines SOA as an architecture that relies on loosely coupled services to support business processes and users. The key benefits of SOA include reusability, linking of resources, and ability to respond quickly to changing market conditions. The document outlines various SOA principles, elements, objectives and technologies used for implementation including web services. It also discusses challenges in adopting SOA such as managing service metadata and security.
REST & RESTful APIs: The State of Confusion
This document discusses REST (Representational State Transfer) and RESTful APIs. It begins by explaining why REST is often misunderstood and discusses common misconceptions. It then covers the origins and constraints of REST as defined by Roy Fielding, including client-server, stateless, cache, uniform interface, layered system and code on demand. It also discusses the Richardson Maturity Model and concludes that REST is the best approach when considering long-term maintenance and evolution, despite having a higher start-up cost than other styles.
Service-oriented Architecture with Respect to Reusability
This document provides an introduction to service-oriented development with a focus on reusability. It includes 4 lectures on topics like introduction to service-oriented architecture, reusability and its relation to SOA, SOA tools, and SOA case studies. The lectures are presented by group members from Shahid Bahonar University of Kerman and cover concepts such as SOA, web services, the SOA lifecycle, and SOA design patterns.
Delivering Process-Driven, Dynamic Applications
The document discusses model-driven business process management (BPM) using template-driven approaches. It proposes that templates can [1] align business concepts with implementations through shared XML representations, [2] enhance interoperability by providing common understandings of data through contextual rules, and [3] support agile development through dynamically configurable templates. The OASIS Content Assembly Mechanism (CAM) is presented as a template standard that can address interoperability challenges by leveraging context and making information exchanges more predictable and adaptable.
Patterns&Antipatternsof SOA
This is a talk I gave on patterns and antipatterns of SOA, based on my understandings and practices and inspired by Ron Jacobs famous webcast by the same name.
Basic concepts of soa
This Dcoument enables readers to have an overview about Service Oriented Architecture (SOA) and its potential benefits.
Why Coordination And Transactions Are Key To Building An Operational Soa
The document discusses the importance of transactions and coordination in building a service-oriented architecture (SOA). Transactions have ACID properties (atomicity, consistency, isolation, durability). There are standards like WS-Coordination and WS-AtomicTransaction that help coordinate distributed services. Coordination is needed to make distributed services function as a single service and reach consistent agreement on outcomes.
CBSE VS SOA SJSU Presentation
It is a presentation of a research paper on Component Based Software Engineering vs Service Oriented Architecture. It deals with basic comparative study of CBSE and SOA , SOA technologies and Service Components, Modern Components. It also covers discussions and justifications of performance issues of web services.
CBSE VS SOA Presentation
This is a presentation of a research paper on comparative study of Component based Software Engineering and Service Oriented Architecture. It covers technologies of both paradigms as well as technical discussions and justifications on SOA. It also covers modern components.
Migrating SOA
This document discusses best practices for migrating to a service-oriented architecture (SOA). It recommends embracing heterogeneity and complexity by abstracting across different software systems using standards like XML and web services. A successful SOA migration requires changing organizational structures and skills to focus on reusable services, incremental changes, and architectural best practices. Service contracts that separate interface from implementation are also key to enabling reuse and flexibility.
Cloud manager client provisioning guideline draft 1.0
Cloud manager client provisioning guideline draft 1.0Sandeep Sharma IIMK Smart City,IoT,Bigdata,Cloud,BI,DW
This document provides guidelines for clients utilizing managed cloud services from a data center. It discusses key considerations including a shift in responsibility and ownership of components to the service provider. It also notes that more parties will be involved and systems need to be integrated. The document outlines roles in a cloud-enabled data center and types of service agreements like SLAs, OLAs, and UCs that define responsibilities. It provides steps for creating service agreements, elements that should be included, and tasks to complete before implementation like defining governance and compliance requirements.Service Oriented Architecture (SOA)
This document discusses Service Oriented Architecture (SOA). It defines key SOA concepts like services, service orientation, and fundamental SOA constructs. It also covers SOA principles, tools, benefits, and the differences between web services and SOA services. Specifically, it notes that SOA aims to reduce costs and complexity by dividing projects into independent and reusable components/services that can be composed to address business needs.
Service Oriented Development With Windows Communication Foundation 2003
This is the presentation on Service Oriented Architecture and Windows Communication Foundation that I gave to the Bartlesville .NET User Group
Brian cappellani scte et 2008 presentation
The document discusses the evolution of services towards greater personalization and on-demand access across multiple technologies. It notes the need for common interfaces to support new types of personalized and on-demand services from both internal and third-party developers. The document argues that open service enablement platforms are needed at the network edge to integrate business rules, subscriber policies and qualifications in real-time to support new types of personalized and blended services from a variety of partners.
More Related Content
Viewers also liked
Japanese Child Care
This document outlines an agenda for presenting on childcare systems in Japan. It will introduce Japan, discuss the formal and informal childcare system including philosophy, age groups, teachers, who pays, and accessibility. It will then compare the similarities and differences between childcare systems and conclude the presentation.
Co branded collateral
This document discusses various partner co-branding and collateral opportunities between ForkFly and traditional media partners, including 30-second television spots, bus advertisements, billboards, distribution boxes, radio advertisements, banner ads on local news sites, web pop-ups, print ads, and branded merchandise for partners in cities such as Monroe, LA, Spokane, WA, Klamath Falls, OR, and others.
Podcasting Education
This document discusses the benefits of using podcasting in education. It notes that podcasting allows for flexibility and accessibility of content for students with different learning styles. While not all students may benefit equally from audio-based instruction, podcasts can be an effective supplement when designed based on an understanding of individual learning preferences. The document provides guidance on how to create podcasts using free, easy-to-use software and export them for playback on digital devices. It concludes that podcasting is a valuable educational tool when it caters to diverse student learning styles.
ForkFly for Media
ForkFly is a self-service platform that allows media partners to monetize digital advertising in new ways and engage advertisers and audiences through their mobile and web apps. It provides geo-targeted deals and incentives to local audiences while giving advertisers tools to build their brand and customer base. Advertisers pay monthly subscriptions for unlimited offers and analytics to understand customer behavior. Media partners can generate revenue through the subscriptions, daily deals programs, and banner ads on their sites.
SCrude Photography Demo
SCrude Photography is a photography business owned by Christopher Kidder that specializes in distorting imagery through unconventional techniques in a single shot. The business can be contacted at 323.839.7893 for photography services that manipulate images in unusual ways with each photo.
Geometry In The Real World
This document defines and describes basic geometric shapes and terms. It defines points, lines, planes, angles, perpendicular and parallel lines, triangles, polygons, quadrilaterals like squares, rectangles, trapezoids and parallelograms, circles, cylinders, spheres, ovals, and properties like concurrent lines and types of quadrilaterals like rhombuses. Key geometric concepts and their definitions are provided to establish common understanding of shape names and characteristics.
Quality of Consumer Experience in the Future Internet
Quality of Experience in the Future Internet era: NEM and the broadcaster\'s perspective. Future Internet Assembly, Stockholm, November 2009.
Viewers also liked (7)
Quality of Consumer Experience in the Future Internet
Quality of Consumer Experience in the Future Internet
Similar to Soa Symposium Rest Style Soa Governance 2009 10 23 Bc
Soa Symposium Expressing Service Capabilities Uniformly 2009 10 14 Bc
The document discusses using a uniform contract to increase integration maturity in service-oriented architectures (SOAs). It proposes expressing service capabilities through resources to create a more abstract interface. The key steps to transform an existing service contract to a uniform contract are outlined, which include splitting nouns from verbs, identifying entity identifiers, and reusing uniform contract elements. Examples of transforming common service operations, like getting prices or making payments, into resource-based interfaces are provided. The benefits of a resource-based approach include enabling runtime discovery and flexible orchestration of services.
Service Oriented Architecture
The document discusses Service Oriented Architecture (SOA). It defines SOA as an architecture that relies on loosely coupled services to support business processes and users. The key benefits of SOA include reusability, linking of resources, and ability to respond quickly to changing market conditions. The document outlines various SOA principles, elements, objectives and technologies used for implementation including web services. It also discusses challenges in adopting SOA such as managing service metadata and security.
REST & RESTful APIs: The State of Confusion
This document discusses REST (Representational State Transfer) and RESTful APIs. It begins by explaining why REST is often misunderstood and discusses common misconceptions. It then covers the origins and constraints of REST as defined by Roy Fielding, including client-server, stateless, cache, uniform interface, layered system and code on demand. It also discusses the Richardson Maturity Model and concludes that REST is the best approach when considering long-term maintenance and evolution, despite having a higher start-up cost than other styles.
Service-oriented Architecture with Respect to Reusability
This document provides an introduction to service-oriented development with a focus on reusability. It includes 4 lectures on topics like introduction to service-oriented architecture, reusability and its relation to SOA, SOA tools, and SOA case studies. The lectures are presented by group members from Shahid Bahonar University of Kerman and cover concepts such as SOA, web services, the SOA lifecycle, and SOA design patterns.
Delivering Process-Driven, Dynamic Applications
The document discusses model-driven business process management (BPM) using template-driven approaches. It proposes that templates can [1] align business concepts with implementations through shared XML representations, [2] enhance interoperability by providing common understandings of data through contextual rules, and [3] support agile development through dynamically configurable templates. The OASIS Content Assembly Mechanism (CAM) is presented as a template standard that can address interoperability challenges by leveraging context and making information exchanges more predictable and adaptable.
Patterns&Antipatternsof SOA
This is a talk I gave on patterns and antipatterns of SOA, based on my understandings and practices and inspired by Ron Jacobs famous webcast by the same name.
Basic concepts of soa
This Dcoument enables readers to have an overview about Service Oriented Architecture (SOA) and its potential benefits.
Why Coordination And Transactions Are Key To Building An Operational Soa
The document discusses the importance of transactions and coordination in building a service-oriented architecture (SOA). Transactions have ACID properties (atomicity, consistency, isolation, durability). There are standards like WS-Coordination and WS-AtomicTransaction that help coordinate distributed services. Coordination is needed to make distributed services function as a single service and reach consistent agreement on outcomes.
CBSE VS SOA SJSU Presentation
It is a presentation of a research paper on Component Based Software Engineering vs Service Oriented Architecture. It deals with basic comparative study of CBSE and SOA , SOA technologies and Service Components, Modern Components. It also covers discussions and justifications of performance issues of web services.
CBSE VS SOA Presentation
This is a presentation of a research paper on comparative study of Component based Software Engineering and Service Oriented Architecture. It covers technologies of both paradigms as well as technical discussions and justifications on SOA. It also covers modern components.
Migrating SOA
This document discusses best practices for migrating to a service-oriented architecture (SOA). It recommends embracing heterogeneity and complexity by abstracting across different software systems using standards like XML and web services. A successful SOA migration requires changing organizational structures and skills to focus on reusable services, incremental changes, and architectural best practices. Service contracts that separate interface from implementation are also key to enabling reuse and flexibility.
Cloud manager client provisioning guideline draft 1.0
Cloud manager client provisioning guideline draft 1.0Sandeep Sharma IIMK Smart City,IoT,Bigdata,Cloud,BI,DW
This document provides guidelines for clients utilizing managed cloud services from a data center. It discusses key considerations including a shift in responsibility and ownership of components to the service provider. It also notes that more parties will be involved and systems need to be integrated. The document outlines roles in a cloud-enabled data center and types of service agreements like SLAs, OLAs, and UCs that define responsibilities. It provides steps for creating service agreements, elements that should be included, and tasks to complete before implementation like defining governance and compliance requirements.Service Oriented Architecture (SOA)
This document discusses Service Oriented Architecture (SOA). It defines key SOA concepts like services, service orientation, and fundamental SOA constructs. It also covers SOA principles, tools, benefits, and the differences between web services and SOA services. Specifically, it notes that SOA aims to reduce costs and complexity by dividing projects into independent and reusable components/services that can be composed to address business needs.
Service Oriented Development With Windows Communication Foundation 2003
This is the presentation on Service Oriented Architecture and Windows Communication Foundation that I gave to the Bartlesville .NET User Group
Brian cappellani scte et 2008 presentation
The document discusses the evolution of services towards greater personalization and on-demand access across multiple technologies. It notes the need for common interfaces to support new types of personalized and on-demand services from both internal and third-party developers. The document argues that open service enablement platforms are needed at the network edge to integrate business rules, subscriber policies and qualifications in real-time to support new types of personalized and blended services from a variety of partners.
Mini-Training: Let's have a rest
A quick overview on REST : what it is and what it is not. REST has strict contraints and many internet Apis are not so REST. It’s also very popular today because RESTfull services can be consumed easily by any client or device. Soap is also still valid in a few circomstaces. It has never been so easy to create Rest-like services in .net since asp.net Web Api.
200211 Fielding Apachecon
The document discusses the design of a new application protocol called Waka, which is intended to address some of the current problems with HTTP while maintaining compatibility with the REST architectural style. Waka would have new request and response semantics to make messages more self-descriptive and efficient. It is in early stages of design and has not yet been implemented or deployed, but is intended to eventually be proposed as an Apache project and submitted to the IETF for standardization.
SOA in banking issues and remedies
This document discusses service-oriented architecture (SOA) in banking and outlines some key benefits and challenges. SOA can benefit banking by enabling customer information management across systems, multi-channel integration, operational excellence through business process automation, and intelligent inbound cross-selling. However, performance issues may arise with SOA implementations due to their distributed nature. To address this, the document emphasizes the importance of service level agreements, infrastructure capacity planning, SOA performance testing, and monitoring systems to ensure performance meets requirements.
SOA architecture patterns, Matjaž Jurič (FRI/Univerza v Ljubljani)
This document discusses SOA architectural patterns and antipatterns. It begins by defining the objective of SOA patterns as enabling loosely-coupled, standards-based architectures. It then describes several common antipatterns that represent bad practices like tight coupling. The document outlines typical SOA architecture components and then provides examples of specific SOA patterns and antipatterns related to areas like services, processes, integration and governance. It concludes by mentioning the IBM SOMA methodology for service-oriented modeling and architecture.
Introduction to SOA
Service Oriented Architecture (SOA) is an architectural style that models systems as a collection of services. Key constructs of SOA include services, service consumers, providers, brokers and registries. Services in SOA are designed to be discoverable, self-describing, and loosely coupled. Benefits of SOA include increased flexibility, reuse, integration and reduced complexity for systems and processes.
Similar to Soa Symposium Rest Style Soa Governance 2009 10 23 Bc (20)
Soa Symposium Expressing Service Capabilities Uniformly 2009 10 14 Bc
Soa Symposium Expressing Service Capabilities Uniformly 2009 10 14 Bc
Service-oriented Architecture with Respect to Reusability
Service-oriented Architecture with Respect to Reusability
Why Coordination And Transactions Are Key To Building An Operational Soa
Why Coordination And Transactions Are Key To Building An Operational Soa
Cloud manager client provisioning guideline draft 1.0
Cloud manager client provisioning guideline draft 1.0
Service Oriented Development With Windows Communication Foundation 2003
Service Oriented Development With Windows Communication Foundation 2003
SOA architecture patterns, Matjaž Jurič (FRI/Univerza v Ljubljani)
SOA architecture patterns, Matjaž Jurič (FRI/Univerza v Ljubljani)
Soa Symposium Rest Style Soa Governance 2009 10 23 Bc
- 1. Governing REST-style SOA Benjamin Carlyle
- 5. REST Technology Impact Uniform Contract and Stateless Constraints
- 8. REST Process Impact New and modified processes
- 11. REST Organisational Impact Uniform Contract Governance within your organization
- 13. Uniform Contract Change Management Objectives, overview, and walkthrough
- 15. Uniform Contract Methods and Media Types
- 16. Change Management Walk-through Canonical Methods and Communication Patterns
- 20. Change Management Walk-through Canonical Media Types, Data Models and Schemas
- 24. Service Change Management Service Description and Service Capability Metadata