For a CustomerRepository service, you might establish a set of data quality KPI. I.e. how many of the customers which have been updated within the last 3 months. The completeness of addresses, email and phone numbers on the customer base, the collaboration between organizational usage and ownership of a customer segment and the like. Technical KPI like response time, availability and the service SLA/contractual parts are also easily exposed and helps the organization to maximize the value of their SOA strategy.
- WebServices can lead to function oriented services, while REST can lead to a resource oriented architecture. Are both SOA?
- I don't think I understand what's meant with law 4 and 5 (I understand the words, but not what you want people to do and when)
- I think I agree with law 3, Establish service ownership and Key Performance Indicators for your services, but an example of a KPI would be helpful
- I think I agree with law 8, Security is not optional in SOA, but I don't understand what you mean by it yet
- In SOA - Is my customer the same entity as your customer? Is my product list the same as your product list? In which situations?
- [Question still to be asked..]
NB! Feel free to add any question you might have here