Contemporary SOA increases quality of service
There is a definite need to bring SOA to a point where it
can implement enterprise-levelfunctionality as safely and reliably as the
more established distributed architectures already do.
This relates to common quality of service requirements, such
as:
- The ability for tasks to be carried out in a secure manner, protecting the contents of a message, as well as access to individual services.
- Allowing tasks to be carried out reliably so that message delivery or notification of failed delivery can be guaranteed .
- Performance requirements to ensure that the overhead imposed by SOAP message and XML content processing does not inhibit the execution of a task.
- Transactional capabilities to protect the integrity of specific business tasks with a guarantee that should the task fail, exception logic is executed.
Contemporary SOA is striving to fill the QoS gaps of
the primitive SOA model. Many of the concepts and specifications we
discuss in Part IISOA and WS-* Extensions provide features that
directly address quality of service requirements. For lack of a better term,
we'll refer to an SOA that fulfills specific quality of service requirements as
"QoS-capable."
No comments:
Post a Comment