In my experience, a conceptual understanding of what is a service is killing SOA. I'd like to believe after the last 14 years that I have built a good experience base for design of services (that includes CORBA). I design nice service-oriented boundaries and software engineers look at it and just go straight for the tightly-coupled modeled and then tell me, "no, it's not tightly-coupled because it's based on an interface."
Interface-based design and design-by-contract are not one-in-the-same, but as long as a majority of individuals implementing SOA don't understand this delicate delineation, SOA will suffer. Clearly, for many software engineers, they see a service as a reusable component, while for many of us that have been at this game awhile, we see a service as a more declarative entity oriented strongly toward a business bent. Having to share SOA design with engineers that don't get it has consistently led to a failure to move forward with the SOA design in favor of a modified component-oriented design. Hence, failed SOA. On Thu Jul 17 11:49:20 CDT 2008, jeffrschneider <[EMAIL PROTECTED]> wrote: > > > > Is governance killing SOA? > > > > Thanks, > Jeff Schneider > > >
