The concept of Web services has seen more than its fair share of media
coverage over the last year. And so has the concept of service-oriented
architectures, which is the use of Web services to define a model of loose
coupling between applications. But the industry buzz regarding this latest
"Next Big Thing" is surprisingly devoid of one important aspect that will
mean the difference between the success and failure of Web services or
service-oriented architectures - management.
Simply put, without the proper management of Web services deployments,
enterprises will not see the business agility or improvements in developer
productivity that they had hoped for. Instead, it is likely that they will
find themselves in a chaotic mess with reduced qualities of service and
hig... (more)
Ever since batch computing and keypunch cards, IT has been obliged to become
increasingly responsive to the enterprise and faster at adapting technology
to meet business needs. Right now businesses' upcoming need is for
e-services, because IT's core competency is becoming the managing of IT
policies and knowing how to leverage technology in support of the business,
without necessarily ha... (more)
As the name suggests, a Service Oriented Architecture is one where
application functionality is packaged as autonomous services that adhere to
industry standard interfaces (WSDL, SOAP), and the services are then deployed
in an IT architecture that makes for their most effective use.
The component services can be rapidly reused and composited, plugged and
played as it were, to create new ... (more)