I seem to have hit a nerve with my last post "SOA vendors focus too much on integration and not enough on architecture." You can read the comments, but the reaction was: Vendors…no like (based on IP addresses). End users…confused (based on IP addresses). Let me be clearer. A few core reactions and my guidance. SOA vendors don't need to understand architecture. They do indeed, this includes architecture in genera I seem to have hit a nerve with my last post “SOA vendors focus too much on integration and not enough on architecture.” You can read the comments, but the reaction was: Vendors…no like (based on IP addresses). End users…confused (based on IP addresses). Let me be clearer. A few core reactions and my guidance. SOA vendors don’t need to understand architecture. They do indeed, this includes architecture in general, and “an architecture” specifically…yours for instance. The fact of the matter is that when you’re selling technology, it’s a tad helpful if you understand its logical fit within the SOA. I’m surprised I have to keep explaining this, but there are those out there that think that tactical selling of this type of technology is the most productive approach, it’s clearly not if you’ve seen the results. VDA, or vendor driven architecture, is killing SOA. Not that the vendors are evil guys tricking end users, but the lack of architectural consideration, on both sides, means you’re selecting the improper technology in many instances. But, integration is important Dave. You bet it is, but it’s not architecture, it’s a part of architecture. Architecture is the orderly creation, placement, configuration, and management of IT assets, and integration is a core architectural pattern. Indeed, without the notion of integration SOA would not do the job now would it? Systems need communications at both the information (data) and behavior levels (service), including mediation of the different formats, semantics, protocol, APIs, etc. However, the more holistic concept is architecture, and you can’t do integration without understanding the architectural context. This includes vendors and enterprise/SOA architects, working together. I suspect that this won’t be well received by the SOA vendors out there, based on the reaction from the last post, and me tracking where those comments came from. However, it’s tough love. You better figure out how to sell technology with the heart of a teacher, and not the heart of a salesman, else you’ll find that your customers won’t find you helpful in the long run. The good vendors understand that, and end users really should ask the tough questions up front. Software Development