* Determine if Web services will be used to access business logic or data. Data access may still be more reliable via alternate methods.
* If services are to be executed in real time and are mission critical, design and topography should be well-thought-out to guarantee availability of the services.
* Evaluate internal skills. Web services cross networks, platforms, operating systems and various application services, requiring competent teams to avoid the pitfalls.
* While companies may want to preserve investment in the existing technical infrastructure, patching across multiple legacy networks and systems may severely impact Web-services performance.
* With Web services, security can not be an afterthought.
* Web-services monitoring tools are a worthwhile investment for problem-solving and performance tuning.
* Process stakeholders across the enterprise should be involved early in the Web-services design cycle.
April 15, 2006
Copyright 2006© LRP Publications