http://www.magpiebrain.com/blog/2005/09/26/the-importance-of-the-word-service-in-webservice/ Sam Newman's blog Wed, 08 Oct 2008 07:08:15 +0000 http://wordpress.org/?v=2.5.1 http://www.magpiebrain.com/blog/2005/09/26/the-importance-of-the-word-service-in-webservice/#comment-938 David Flett Fri, 14 Oct 2005 21:06:12 +0000 http://www.magpiebrain.com/2005/09/26/the-importance-of-the-word-service-in-webservice/#comment-938 You're correct of course Sam but you are also stating the obvious. An enterprise's decision to move to an SOA based on Web services is a strategic one, not a technical one. While current Web service world is an interesting one to be in (I am now 100% on Web service projects) and the new standards promise much, the real deal for an enterprise is the value the service offers to the business not the technolgy used to implement it. Businesses (banks in particular) have been defining these 'service parameters' for years. Currently many are 'out of band' although XML namespaces provide the message standard versioning businesses must rely upon. What is new and interesting in the SOA world nowadays is both the promising new standards being proposed for business integration, service quality, business process management and the level to which these new SOA standards are being supported by middleware vendors such as IBM, Microsoft, Oracle, etc. Many currently criticize the Web service world, especially those in the RESTful community (I think) but the value is in the new standards coming forward. WSDL in particular is making a real difference in the back offices of the worlds financial institutions. You’re correct of course Sam but you are also stating the obvious. An enterprise’s decision to move to an SOA based on Web services is a strategic one, not a technical one. While current Web service world is an interesting one to be in (I am now 100% on Web service projects) and the new standards promise much, the real deal for an enterprise is the value the service offers to the business not the technolgy used to implement it. Businesses (banks in particular) have been defining these ‘service parameters’ for years. Currently many are ‘out of band’ although XML namespaces provide the message standard versioning businesses must rely upon. What is new and interesting in the SOA world nowadays is both the promising new standards being proposed for business integration, service quality, business process management and the level to which these new SOA standards are being supported by middleware vendors such as IBM, Microsoft, Oracle, etc. Many currently criticize the Web service world, especially those in the RESTful community (I think) but the value is in the new standards coming forward. WSDL in particular is making a real difference in the back offices of the worlds financial institutions.

]]> http://www.magpiebrain.com/blog/2005/09/26/the-importance-of-the-word-service-in-webservice/#comment-937 David Flett Fri, 14 Oct 2005 21:02:18 +0000 http://www.magpiebrain.com/2005/09/26/the-importance-of-the-word-service-in-webservice/#comment-937 You're correct of course Sam but you are also stating the obvious. An enterprise's decision to move to an SOA based on Web services is a strategic one, not a technical one. While current Web service world is an interesting one to be in (I am now 100% on Web service projects) and the new standards promise much, the real deal for an enterprise is the value the service offers to the business not the technolgy used to implement it. Businesses (SWIFT in particular) have been defining these 'service parameters' for years. Currently many are 'out of band' although XML namespaces provide the message standard versioning businesses must rely upon. What is new and interesting in the SOA world nowadays is both the promising new standards being proposed for business integration, service quality, business process management and the level to which these new SOA standards are being supported by middleware vendors such as IBM, Microsoft, Oracle, etc. Many currently criticize the Web service world, especially those in the RESTful community (I think) but the value is in the new standards coming forward. WSDL in particular is making a real difference in the back offices of the worlds financial institutions. You’re correct of course Sam but you are also stating the obvious. An enterprise’s decision to move to an SOA based on Web services is a strategic one, not a technical one. While current Web service world is an interesting one to be in (I am now 100% on Web service projects) and the new standards promise much, the real deal for an enterprise is the value the service offers to the business not the technolgy used to implement it. Businesses (SWIFT in particular) have been defining these ‘service parameters’ for years. Currently many are ‘out of band’ although XML namespaces provide the message standard versioning businesses must rely upon. What is new and interesting in the SOA world nowadays is both the promising new standards being proposed for business integration, service quality, business process management and the level to which these new SOA standards are being supported by middleware vendors such as IBM, Microsoft, Oracle, etc. Many currently criticize the Web service world, especially those in the RESTful community (I think) but the value is in the new standards coming forward. WSDL in particular is making a real difference in the back offices of the worlds financial institutions.

]]> http://www.magpiebrain.com/blog/2005/09/26/the-importance-of-the-word-service-in-webservice/#comment-936 Jason Yip Tue, 27 Sep 2005 08:26:35 +0000 http://www.magpiebrain.com/2005/09/26/the-importance-of-the-word-service-in-webservice/#comment-936 I'd say that "service" should also mean that web services are there to serve the projects' needs and the projects are not there to serve the web services. That is, there should be an obligation for a service to prove its worth to projects and projects should not be required to use them. I’d say that “service” should also mean that web services are there to serve the projects’ needs and the projects are not there to serve the web services. That is, there should be an obligation for a service to prove its worth to projects and projects should not be required to use them.

]]>