The basic assumption that underlies Service Oriented Architecture is the idea that reusable Services exist. The enterprise has, on hand, really useful Services that can be choreographed with each other to produce Composite Applications. Sadly, this assumption is rarely accurate, but even when existing Services are available, this is a bottom-up approach to building Solutions.
When developing a Solution, it's very useful to make use of existing Services... but that's not where you start. You don't start out by taking an inventory of all the Services that are available that might help solve a specific problem... You start by figuring out the steps that are necessary to solve the problem, and then identifying existing Services that might help you perform one or more of the steps.
Services, and infrastructure that makes them easy to utilize, are incredibly important - but Solution Development tools, such as BPM suites, are where you need to start.
No comments:
Post a Comment