Last post Mar 04, 2010 12:15 AM by Song-Tian - MSFT
Mar 02, 2010 02:41 AM|Das.Sandeep|LINK
I am using SOA architecture, any one please guide me what major and minor thing we need to take in long running.
Thanks in advance.
Mar 02, 2010 03:21 AM|qwe123kids|LINK
SOA(service orinted Architecture) Webservice and WCF will Take care..
Mar 02, 2010 09:44 AM|atconway|LINK
Here are some of the 'Pitfalls' of SOA you may want to be aware of going forward:
Avoiding common pitfalls in SOA adoption:
Top 8 SOA Adoption Pitfalls:
Top 10 SOA Pitfalls:
Avoid SOA Pitfalls!
Mar 04, 2010 12:15 AM|Song-Tian - MSFT|LINK
SOA confers obvious business benefits associated with integration and the creation of new services. However, insufficient attention to governance—the management and monitoring of services, their performance and reliability, and especially their security—can
cause inefficiencies and disrupt business processes and the end users they support. As business needs evolve, it is critical to have policies in place that help determine how to prioritize new business processes and services under consideration for implementation,
who will be responsible for designing those processes, how they should be implemented, and how the success of the new implementations will be measured. This is especially important given the inherent cross-functional nature of SOA solutions.
Reuse of services, once touted as a primary SOA advantage, is really a byproduct of the approach rather than the goal itself. Reuse is also proving to be more challenging than expected. An existing service may not provide exactly what a different business
process requires and so may call for additional work. And designing a service so that it can be reused in the future requires accurately predicting what future needs will be, something notoriously difficult to do.