It is interesting that this question has been posed. How were you planning to describe such performance information anyway? The challenge in this area is that there is no WS-Policy based standard for asserting performance or SLA information yet. However, I would expect that the standards will evolve to address this issue.
For now, I would advise to keep track of meta-data, including performance and SLA information in a SOA registry. Registries today allow you to specify information such as execution time and service availability metrics, and allow to be extended for more. The specific metrics you select depend on what your consumers are looking for, but it is important to find a way to maintain and update such performance metrics so they don't become outdated. Your Web services management (when the service is in production) or testing products (while it is being evolved before production) can feed the latest performance data into the registry, otherwise such information would become unreliable if it is left for manual updates.
Dig Deeper on Topics Archive
Related Q&A from Rami Jaamour
Rami Jaamour discusses how to go about planning on using emulation in order to simplify complexity or replicate the behavior of systems that are ... Continue Reading
Rami Jaamour discusses the best place to begin when building a testing system for SOA and how to establish a quality policy as part of the overall ... Continue Reading
Rami Jaamour suggests business process simulation and business process testing for optimizing BPM and realizing the ROI. Continue Reading