Jump to: navigation, search

Orion/Planning Meeting/Server integration

< Orion‎ | Planning Meeting
Revision as of 14:50, 18 March 2011 by John arthorne.ca.ibm.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Back end API for data store to enable deployment to cloud environments for example

    • Store JSON for metadata
    • Persist relationships between services

How does the search service know where to get the data from Particular client side plugins know how to interact with particular server side services

Some composite services

  • Some services depend on other services
  • Service discovery
    • REST principles via links
    • Currently have runtime service link injection

No solution yet for cross-domain server integration

    • How does resource link injection work when services reside in different processes, or on different domains

  • OSLC allows data linking between development artifacts in the development tool domain
  • Similar data linking approach could be used in other domains

How can I write a service that adds extra data to the output of another service

Service to service contracts

    • What do I allow another service to do
  • Use Pubsub for inter-service collaboration
    • File service publishes information on file changes, and search indexer subscribes (for example)
    • HubBubPubSub
    • RSS feeds
    • Atom pub

Push model for server announcing changes back to client

  • Same PubSub mechanism for server-server interaction could be used for client notification
  • Integration of link to RSS feed or whatever done at the client
  • California is not as sunny as we thought