With the large-scale grass-roots adoption of Web services, management must be planned for - but it can't be treated in the traditional way. In the past, applications were monoliths which were (for the most part) operationally independent of each other. With the adoption of web services this all changes - applications by themselves are just one piece of the whole solution. A given request will flow across multiple different systems in the course of being processed. Managing and understanding the interrelationships becomes as important as managing the individual parts that make up the whole. A problem or change in any one part can have ripple effects throughout the whole that must be identified, controlled, and contained. The management challenges are significant: security, availability, versioning, monitoring, and capacity planning are just a few of the categories that must be considered across the whole, rather than individually at each part. Luckily, Web services management solutions are available to complement traditional management solutions to manage an overall Web service network.
Dig Deeper on Topics Archive
Related Q&A from Daniel Foody
Daniel Foody defines end-to-end security and discusses the different parts of security to consider. Continue Reading
Dan Foody discusses the capability of using Web services for ASP applications. Continue Reading
Daniel Foody discusses the "find-bind-execute" paradigm and secure service directories. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.