Architectures:

1. Service oriented architecture
    From the oracle IDC paper:

•     Requirements
•     Design principles
•     Architectural features

2.  Requirements:

•  Loosely coupled ( See what is Service Oriented Architecture  by Hao He)

        An architectural style whose goal is to achieve loose coupling among interacting agents
        Significantly different from OO: CD with player (OO), CD and player offered by different agents (SOA)

•  Service encapsulation

       Separation of the interface to the service and detailed internal specification and implementation of the service.

•   Interface standardization
  

      Interfaces should be simple and ubiquitous; universally  availableto producers and consumers; Must have a mechanism for
      discovery of the these services through' the interfaces.

• Shared semantic framework

       Descriptive messages constrained by an extensible scheme delivered through the interfaces; An extensible scheme allows
       new versions of the services to be introduced without breaking existing services;
       messages must be descriptive, standard, extensible;
     

3, Design principles:

• Service discovery: provides a mechanism to locate and provision
• Service security
• Service oriented management
• Service integration
• Event driven architecture
• Service provisioning
• service rendering
• service development
• life cycle management

4. Reference model:
    Platform services: deployment services, integration services, process orchestration, policy, state management  
    Support services: Access services, development facilities, security and management services, application and data services
    Process orchestration: Organizes and aggregates services into flows to automate system and business processes.
     State Management: Ability to recognize, support and manage entity state

5. Role Standards: standard bodies: WS-I, W3C, OASIS, Liberty (Alliance)

6. Service Grids: The Missing Link in Web Services ( by J. Hagel III and J.S. Brown)
    Most existing work: standards and protocols and application services enabled by these standards and protocols;
    The paper focuses on architecture + environment (business ecology)

• WS and Peer-to-Peer
• Importance of managed services: service grid is analogous to power grid in this case ; provide trusted services, secure services,
• auditing and assessment, monitoring, directories, brokers, queuing, filtering, resource orchestration.. See Figure 1
• Utilities within service grids: shared utilities, transport management utilities, resource management, service managment (SLAs)
• Where will a service grid reside? How will they look?
• network overlay
• federation of service utilities (loosely couple federation of utilities)
• In business environments: service integrators and aggregators, enablers for service utilities;
• Significance of "service grid"
• Providing mission critical functionality: secure connections, monitoring, QoS (perf), etc.
• Easing task of discovering appropriate web services
• Enabling revenue generation for WS
• Acceleration of adoption of WS technology
• Reducing complexity at the ends/edges: makes it simpler for end-points to connect
• Bootstrapping existing technology
• Mediating among competing standards and policies
• Developing shared semantics
• Any existing solutions? Grid computing is one..
• Others: read the paper.