A Resource Oriented Framework for Context-Aware Enterprise ApplicationsWS-REST 2011Hyderabad, IndiaMarch 28, 2011<br />Dav...
Presentation Flow<br />1. Background <br /><ul><li>A Resource-Oriented Framework
Out-of-Band Context
Connectedness - It’s a Small World After All
READ-WRITE-EXECUTE
Emergent Process
Implementations</li></ul>2. System Design<br /><ul><li>Everything is a Resource
Distributed
Virtualized Information Layer
A Canonical Method
Conceptual Architecture</li></ul>3. Relationship to REST<br /><ul><li>Alignment with REST Constraints</li></ul>4. Referenc...
A Resource-Oriented Framework<br />A Context-Aware Information System implemented as a RESTful Intermediary. <br />All sys...
Out-of-Band Context<br />The System exploits out-of-band context to return targeted responses that optimize business relev...
Upcoming SlideShare
Loading in...5
×

Ideate Framework WS-REST 2011

2,380

Published on

Ideate Framework (www.ideate.com). Presented at WS-REST 2011, Hyderabad India. A Resource-Oriented Framework that can dynamically coordinate resources in a virtual information layer to perform as services, without middleware indirection. Ideate delivers the Read-Write-Execute Web.

Published in: Technology, Education
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,380
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • No compiled system code, everything is a Resource, no native encapsulation – flexibility of representation - maximum latent potential for transformationA sole first class citizen, lends generality to the system and allows for common treatment across all Resources or a subset by Type, facilitates code-on-demand. Every ‘media type’ paired with a utility (e.g. XML with Saxon, Rule with DROOLS, a report definition with Pentaho, etc.).
  • Graph Information model. Loosely-coupled resources with complete separation of concerns – Resources related by metadata tags. Locality of Code, Code Mobility. an ideal environment for enterprise mashups.
  • Convergence of EAI, ETL and BI
  • Ideate Framework WS-REST 2011

    1. 1. A Resource Oriented Framework for Context-Aware Enterprise ApplicationsWS-REST 2011Hyderabad, IndiaMarch 28, 2011<br />Dave Duggal<br />Consilience International LLC<br />dave@ideate.com<br />William Malyk<br />Consilience International LLC<br />bill@ideate.com <br />Copyright 2011, Consilience International LLC<br />
    2. 2. Presentation Flow<br />1. Background <br /><ul><li>A Resource-Oriented Framework
    3. 3. Out-of-Band Context
    4. 4. Connectedness - It’s a Small World After All
    5. 5. READ-WRITE-EXECUTE
    6. 6. Emergent Process
    7. 7. Implementations</li></ul>2. System Design<br /><ul><li>Everything is a Resource
    8. 8. Distributed
    9. 9. Virtualized Information Layer
    10. 10. A Canonical Method
    11. 11. Conceptual Architecture</li></ul>3. Relationship to REST<br /><ul><li>Alignment with REST Constraints</li></ul>4. References<br />2<br />Copyright 2011, Consilience International LLC<br />
    12. 12. A Resource-Oriented Framework<br />A Context-Aware Information System implemented as a RESTful Intermediary. <br />All system communications are based on a Uniform Interface.<br />Clients traverse links consistent with HATEOAS.<br />Generative - all payloads, including generalized next steps, are generated dynamically<br />No Domain Specific Languages, just generalized capabilities from coordinated Resources. <br />A Framework for Situationally-Aware Composite Applications and Emergent Process.<br />3<br />Copyright 2011, Consilience International LLC<br />
    13. 13. Out-of-Band Context<br />The System exploits out-of-band context to return targeted responses that optimize business relevance and support precise in-flight application of policies (i.e. business rules; system governance; transaction controls). <br />Out-of-Band context includes any URI accessible to the system via its virtual information layer (e.g. data; business entities; program code; RESTful Services; RESTfully encapsulated legacy systems; etc.).<br />Responses are run-time constructions because context is temporal.<br />The System provides Lifecycle Management of all system Resources with automatic version control and roll-back capability. Version is part of context, applications co-evolve with their constituent Resources.<br />4<br />Copyright 2011, Consilience International LLC<br />
    14. 14. Connectedness - It’s a Small World After All<br />Virtual Information layer induces a graph information model, the system is a ‘Small World Network’.<br />An Agent fetches Out-of-Band Context based on machine and user generated metadata tags as guided by Metaprograms and policies.<br />5<br />Copyright 2011, Consilience International LLC<br />
    15. 15. READ-WRITE-EXECUTE<br />Coordinates loosely-coupled Resources (Nouns) to act like Services (Verbs) without the cost, indirection, or latency of middleware-centric approaches (i.e. no ESB, BPEL, BPMN, CEP, etc). <br />Interoperability with the opportunity to consolidate patterns by devolving capabilities from middleware to generalizable capabilities of a system of systems.<br />Moves web from Read/Write (CRUD) to Read/Write/Execute, where execute is RESTful coordination of loosely-coupled distributed Resources.<br />6<br />Copyright 2011, Consilience International LLC<br />
    16. 16. Emergent Process<br />Interaction-driven system supports emergent processes without limitations of finite state map.<br />The degree of structure (i.e. control logic) is a runtime variable. The system balances interests, as flexible as possible for business relevance and as procedural as necessary for compliance. <br />Addresses a gap in process collaboration technologies; current product offerings are either too rigid (e.g. ERP; Expert Systems; BPMS; etc.) or too ad hoc (e.g. activity streams; email; case management).<br />7<br />Copyright 2011, Consilience International LLC<br />
    17. 17. Implementations<br />Targeted at complex, long-running, human-centered, indeterminate goal-driven work that are impacted by events and characterized by exceptions – ‘knowledge-work’.<br />Initially focused on R&D sector with deployments and test sites around the world, and in discussions with Enterprise Architects at Financial Companies, Hotel Chains, and other Industries.<br />8<br />Copyright 2011, Consilience International LLC<br />
    18. 18. Everything is a Resource<br />A Sole First-Class Citizen<br />Data/Entities<br />Program Code/Meta-Programs<br />Services<br />Legacy Systems<br />9<br />Copyright 2011, Consilience International LLC<br />
    19. 19. Distributed<br />Data/Entities<br />Program Code<br />Services<br />Legacy Systems<br />10<br />Copyright 2011, Consilience International LLC<br />
    20. 20. Virtualized Information Layer<br />Data/Entities<br />Program Code<br />Services<br />Legacy Systems<br />11<br />Copyright 2011, Consilience International LLC<br />
    21. 21. A Canonical Method<br />Mashup as Information Integration Model<br />Request<br />Resourcesn<br />Intermediary<br />Custom Response<br />∞<br />Utilitiesn<br />Resource Representation<br />Step 1: Serial Mash-up to Progressively Evaluate what Generalized Action is Required<br />Step 2: Serial Mash-up to Progressively Customize Generalized Action<br />Step 3: Serial Mash-up to Identify Valid Transitions (Next Possible Generalized Actions)<br />Deliver Custom System Response, Update Resource Lifecycles, Dissolve Container<br />12<br />Copyright 2011, Consilience International LLC<br />
    22. 22. Dave Duggal<br />Consilience International LLC<br />dave@ideate.com <br />William Malyk<br />Consilience International LLC<br />bill@ideate.com <br />www.ideate.com<br />Copyright 2011, Consilience International LLC<br />

    ×