21 December 06 - 18:07Web services vs. Business Component Specification

Tags: bpm, business_process, component, service_oriented_architecture, soa, standard, web_service
The use of web services is still growing fast. This isn’t very strange because the use of web services could have a lot advantages. If you read the websites of big vendors in this area (SOA, webservices), you mostly see promises like: increased flexibility, more reuse, etc. If you go a little deeper and look at the future visions you see in most of the cases a market separated in three parts: service platform providers, service directories and service aggregators.

In this picture service aggregators search for the right service in service directories and assemble them together forming a business solution. The service platform providers deliver the middleware through which the services can work together. This last part is already proven in practice, but mostly with in-house developed services. The real benefit you can get out of such an architecture should come from the smart selection of web services out of service directories by the service aggregators. To do this well we need standardized techniques for specifying this services. On this topic I want to elaborate a bit, because, in my opinion, a lot of work is needed to make this all work nice and smooth.

I want to make a comparison between the current web service specification standards and (more)

- Enterprise architecture - No comments / No trackbacks - § ¶