The RESTful Soa Datagrid with Oracle

21,203 views

Published on

It transforms and caches any SOA based application in REST. A proxy "soap to rest" is provided, using Oracle Service Bus and Oracle Coherence.

Published in: Technology
3 Comments
10 Likes
Statistics
Notes
  • good materials. thanks for sharing
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Very interest article.
    Do you have any performance test result about this architecture?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Now embedded at www.ukocn.com

    http://www.ukocn.com/forums/oracle-fusion-middleware/middleware-white-papers-and-presentations/restful-soa-datagrid-oracl

    About UKOCN

    UKOCN is your primary resource for informative, up-to-date Oracle community news, updates, Partners innovations and more within the UK. Join today to get total access to the most relevant information to you - white papers, press releases, presentations, data sheets, special offers, training, events, jobs and more.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
21,203
On SlideShare
0
From Embeds
0
Number of Embeds
5,757
Actions
Shares
0
Downloads
382
Comments
3
Likes
10
Embeds 0
No embeds

No notes for slide
  • The RESTful Soa Datagrid with Oracle

    1. 1. The RESTful SOA Datagrid (restify your world and put it in a cache) Emiliano Pecis Technology Business Unit
    2. 2. Just for fun: some Anti SOA Quotes :) <ul><li>Implementing SOA for the first time is the triumph of imagination over intelligence </li></ul><ul><li>Implementing SOA for the second time is the triumph of hope over experience </li></ul><ul><li>One person successfully described SOA completely, and immediately died </li></ul><ul><li>Guns don't kill people, the SOA WS-* stack kills people </li></ul><ul><li>SOA knows what you did last summer, and is disappointed that it wasn't SOA </li></ul><ul><li>( from soafacts.com ) </li></ul>
    3. 3. Agenda
    4. 4. What is REST
    5. 5. WOA – Web Oriented Architecture
    6. 6. WOA vs SOA
    7. 7. Introducing REST <ul><li>Nouns: All resources, or nouns, are network-addressable with a global URL. Resources have “href” references to other related resources. The only way to address a resource is with a URL. </li></ul><ul><li>Verbs: A common set of verbs are used to access all resources. The HTTP methods GET, PUT, POST, and DELETE map to retrieve, update, create, and delete (CRUD) functions. </li></ul><ul><li>Representations:  A resource might be represented as XML, JSON, HTML, text, image, and so on. Instantiating representation from or to the resource is handled on the server. A client can pick its preferred representation via a URI parameter or the “Accept:” header. </li></ul>
    8. 8. REST Patterns 1/2 <ul><li>Give every “thing” an ID (URI): </li></ul><ul><ul><ul><ul><ul><li>http://example.com/orders/2007/11 </li></ul></ul></ul></ul></ul><ul><li>Link things together (Hypermedia links): </li></ul><ul><ul><ul><ul><ul><li><order self='http://example.com/customers/1234' > <amount>23</amount> <product ref='http://example.com/products/4554' /> <customer ref='http://example.com/customers/1234' /> </order> </li></ul></ul></ul></ul></ul><ul><li>Use standard methods (HTTP verbs) </li></ul><ul><ul><ul><ul><ul><li>GET is safe and idempotent </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>PUT and DELETE are not safe but are idempotent </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>POST is neither safe nor idempotent </li></ul></ul></ul></ul></ul>
    9. 9. REST Patterns 2/2 <ul><li>Resources with multiple representations </li></ul><ul><ul><ul><ul><ul><li>GET /customers/1234 HTTP/1.1 Host: example.com Accept: application/vnd.mycompany.customer+xml </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>GET /customers/1234 HTTP/1.1 Host: example.com Accept: text/x-vcard </li></ul></ul></ul></ul></ul><ul><li>Communicate statelessly </li></ul><ul><ul><ul><ul><ul><li>Cookies shouldn’t be used to encode information that can be transferred by other, more standardized means </li></ul></ul></ul></ul></ul>
    10. 10. REST Anti Patterns <ul><li>Tunneling everything through GET or POST </li></ul><ul><ul><li>http://example.com/some-api?method=deleteCustomer&id=1234 </li></ul></ul><ul><ul><li>Resources are not identified by URIs; rather, URIs are used to encode operations and their parameters </li></ul></ul><ul><ul><li>The HTTP method does not necessarily match the semantics </li></ul></ul><ul><ul><li>Such links are usually not intended to be bookmarked </li></ul></ul><ul><ul><li>There is a risk that “crawlers” (e.g. from search engines such as Google) cause unintended side effects </li></ul></ul><ul><li>Ignoring caching </li></ul><ul><ul><li>Cache-control: no-cache (always) </li></ul></ul><ul><li>Ignoring status code </li></ul><ul><ul><ul><li>Misusing of 200 or 500 status code </li></ul></ul></ul>
    11. 11. Processes and Resources
    12. 12. Oracle parts involved
    13. 13. Parts of the Restful Soa Datagrid
    14. 14. Parts of the Restful Soa Datagrid
    15. 15. Core Value of Service Bus <ul><li>Service Intermediary & Management </li></ul><ul><li>Service Location Transparency </li></ul><ul><li>Service Virtualization </li></ul><ul><li>Any to Any Protocol, Payload </li></ul><ul><li>Configuration </li></ul><ul><li>Advanced Integration Patterns </li></ul><ul><li>High Availability & Scale </li></ul>Oracle Service Bus BPM Portal Adapters B2B & BPM Service Repository Presentation Services Integration Services Service Orchestration Business Logic Business Logic
    16. 16. How Do We Deliver This Data ? Patterns of Services <ul><li>Traditional Web Services </li></ul><ul><ul><li>Pre-negotiated Interfaces Contract (WSDL) </li></ul></ul><ul><ul><li>Standards in place, supported by many vendors </li></ul></ul><ul><ul><li>SOAP over HTTP </li></ul></ul><ul><li>REST (Representational State Transfer) </li></ul><ul><ul><li>Based on Pattern of Service Invocation </li></ul></ul><ul><ul><li>Nouns vs. Verbs </li></ul></ul><ul><ul><li>URIs over HTTP </li></ul></ul><ul><li>RSS (Really Simple Syndication) </li></ul><ul><ul><li>Ad hoc channels of data </li></ul></ul><ul><ul><li>XML format, content unstructured </li></ul></ul><ul><li>POX (Plain Old XML) </li></ul><ul><ul><li>Structure of Payload to determines action </li></ul></ul><ul><ul><li>XML over HTTP </li></ul></ul>
    17. 17. Final Thoughts… Trends Emerging <ul><li>Federated ESB </li></ul><ul><ul><li>Not enough to simply distribute across buses. </li></ul></ul><ul><ul><li>Management is KEY. </li></ul></ul><ul><ul><li>Homogenous until vendors decide on management standards to allow uniform service provisioning & routing updates. </li></ul></ul><ul><li>Event-driven SOA </li></ul><ul><ul><li>Dynamic, unpredictable business events being correlated real-time feeding into SOA infrastructure </li></ul></ul><ul><li>Web 2.0 meets SOA & Traditional IT infrastructure </li></ul><ul><ul><li>Watch out - IT Culture class emerging! </li></ul></ul><ul><ul><li>Service Bus will help adapt Traditional SOA to more ad-hoc services like REST, POX with security. </li></ul></ul>
    18. 18. Parts of the Restful Soa Datagrid
    19. 19. Data Grid Uses Caching Applications request data from the Data Grid rather than backend data sources Analytics Applications ask the Data Grid questions from simple queries to advanced scenario modeling Transactions Data Grid acts as a transactional System of Record, hosting data and business logic Events Automated processing based on event
    20. 20. Data grid as Data Broker <ul><li>Data grid brokers Data Supply with Data Demand </li></ul><ul><li>Scale out Data Grid in middle tier using commodity hardware </li></ul>Application Servers Web Servers Ever Expanding Universe of Users Data Sources Data Demand Java Objects 10110001011001011101100101100101110001110 101100010110010111011001011001011100011101111110001110
    21. 21. Data Grid for SOA Services <ul><li>Coherence Solution </li></ul><ul><li>Developer integration to Coherence APIs into service bus pipeline. </li></ul><ul><li>Named cache created using CacheFactory </li></ul><ul><li>Optionally cache could be implemented in orch. engine or portal </li></ul><ul><li>Benefits </li></ul><ul><li>Up to10 fold reduction in latency times used Cached data </li></ul><ul><li>Cache available to other nodes in the cluster. </li></ul><ul><li>Data grid provides backup of cache to peer Coherence nodes </li></ul><ul><li>Cache can be persisted to the database using a number of mechanisms. </li></ul>Service Bus Portal Orchestration Engine Service Provider [data item] [data item] Service MySelfServPortal Coherence Grid Near Cache Cache This is a very large piece of customer data that has to be obtained in one go from the system.
    22. 22. Parts of the Restful Soa Datagrid
    23. 23. Please do keep in Mind <ul><li>Great work developed by Bassam Hijazi </li></ul><ul><li>It’s a custom work (not supported) </li></ul><ul><li>New to Coherence </li></ul><ul><li>Inbound/Outbound </li></ul><ul><li>The transport only touches the surface of what Coherence has to offer </li></ul>
    24. 24. Coherence Transport Request Payload
    25. 25. Simple Put Request/Response
    26. 26. Restful SOA Datagrid
    27. 27. Restful SOA Datagrid Architecture <ul><ul><li>Oracle Service Bus </li></ul></ul><ul><ul><li>Client side </li></ul></ul><ul><ul><li>Server side </li></ul></ul>
    28. 28. Restful SOA Datagrid: OSB pipeline
    29. 29. RSD: parse the URL http://siebel.com/rsd/catalog/product/id/5461 ?n1=v1&n2=v2… get / put / post / delete
    30. 30. RSD: check if cached Check the cache only if GET method has been used Assign a XML payload to a variable Send the payload to Coherence through the OSB Transport if Coherence is not UP a WS call will be done If the item is not in the cache a WS call will be done) Skipcache variable will be tested to decide if it is the case to return the cached value or invoke the WS
    31. 31. RSD: return cached item If the result has been taken from the cache return it
    32. 32. RSD: set up WS call This is the main configuration file. From this file, RSD is able to match the provided URL with all the parts of a standard WS call: Business Service , the Soap Action , the header and body SOAP with the relative parameters
    33. 33. RSD: the configuration file GET /rsd/catalog/categories/id/3473 The following URI parts select the needed WS parts: This is the SOAP operation to invoke This is the SOAP payload to load This is the SOAP response to return But, what about the URL parameters?
    34. 34. RSD: the configuration file GET /rsd/catalog/categories/id/3473
    35. 35. RSD: the response Get the response Transform from XML to JSON Put it in the cache
    36. 36. RSD: coherence integration <ul><li>A custom OSB transport has been developed for Coherence by Bassam Hijazi </li></ul>
    37. 37. Restful Datagrid Reasonings <ul><li>In REST each resource has a unique URL </li></ul><ul><li>This URL is the primary key for the Datagrid (Coherence) </li></ul><ul><li>The cached value is stored in JSON format to be as “client ready” as possible </li></ul><ul><li>REST and JSON give developers more flexibility, ensuring a strong  light-matter coupling between content and its rapresentation </li></ul><ul><li>Javascript frameworks, like Jquery, allows developers to get JSON data from the datagrid and manipulate them as they prefer </li></ul>
    38. 38. Credits and resources <ul><li>Credits: </li></ul><ul><li>How it all began: Using REST with Oracle Service Bus </li></ul><ul><li>OSB transport: great work developed by Bassam Hijazi </li></ul><ul><li>Interesting article by David Chappel: Not your MOM’s bus </li></ul><ul><li>Resources: </li></ul><ul><li>A Brief Introduction to REST </li></ul><ul><li>Rest Anti-Patterns </li></ul>

    ×