Group items tagged

the separation of business process management as an independent function, allowing processes to be designed independently of any single application and leveraged as shared business logic.

the concept of orchestration is rooted in the fundamental shift of application design towards the delivery of software as a service, evolving from the maturation of both J2EE and Web services.

The process-driven and service-oriented architecture presented by the combination of SOA and BPM provides an ideal environment for building adaptable, model-driven composite applications or "composite apps" from existing IT assets and infrastructure.

QoS covers a whole range of techniques that match the needs of service requestors with those of the service provider's based on the network resources available. By QoS, we refer to non-functional properties of Web services such as performance, reliability, availability, and security.

separate QoS language for Web services

The following steps should be performed during binding establishment using a QoS-enabled Web services platform: The service requestor requests the establishment of the binding by specifying the reference to a Web service interface. This request also contains the required QoS. The QoS broker searches for the service providers in the UDDI. The QoS broker performs QoS negotiation as described below. The Web service QoS broker compares the offered QoS with the required QoS and uses its internal information to determine an agreed QoS. This process is called QoS negotiation. If the QoS negotiation has been successful, the service requestor and service provider are informed that a negotiation has been successful and a binding has been built. From this moment on these objects can interact through the binding.

Web services are a linking and communications methodology. SOA is an overall IT strategy.

it is an architectural strategy, SOA involves much more than merely building software.

Governance is critical