A definition of architecture states that it is the structure of a system and the description of its components and interconnections. As a structure, the architecture exists in any system, no matter how convoluted; and it can be described by an architecture diagram.
For the target state of a system, a blueprint is drawn to describe the desired logical architecture of the system, that is its components and interconnections. This architecture blueprint enters then a design phase where technologies and products are selected for each component and interconnection. The end result, the design blueprint, consists of detailed drawings of the interconnected components of the systems.
The design is ready now for implementation and as such, at last, the architecture is implemented in a physical system out of the interconnected products.
A style of architecture consists of recognisable and reproducible architecture patterns.
SOA is a style of architecture applied to a target system. SOA, as a style, can be equally used in an application or in the target architecture of an Enterprise. SOA architecture, after the design phase, is implemented by the systems delivering the SOA business services.
SOA is at the same time an integration technology for services rather than applications. This is what vendors try to sell you: ESB, registries... based on SOAP/XML, UDDI, WSDL etc. SOA technology integrates and interconnects rather than implements the services of a system. Vendors also offer, in addition, business process (and rules) engines, B2B systems, application servers, service management and other products in their SOA offer.
The SOA business services design and orchestration is what people say you must do, not buy. You do have to specify your business services first and then interconnect them with a SOA technology. Can you say implement SOA services once you specified them? You can. But you can equally say that you buy SOA technology to integrate the systems delivering the business services.
Comments (1)
Written by
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
on 03-06-2008 08:09
Adrian,
I can only say that you "do SOA" but "buy SOA enabling technologies". You could even buy "SOA enabling technologies" and use them without doing SOA, which arguably is what a lot of companies do. Using SOA enabling technologies to integrate the already existing middleware and hence creating another layer of middleware.
So I believe that we should Service Orient around business services (Enterprise SA), deliver that with the architectural style SOA and then make that architecture a reality through "SOA enabling technologies".
Via Nova Architectura is not responsible for the content of blogs, but authors and readers are asked to adhere the following guidelines. Authors are strongly encouraged to check facts, cite sources, present
balanced views, acknowledge and correct errors. Respect copyright, fair use and financial disclosure laws. Please do not disparage organizations, or individuals. Being critical of someone's practice is acceptable, when it is done in a professional manner. Prevent usage of marketing statements. Comments should be relevant to the specific post they are attached to. Spam, flaming, personal attacks, and off-topic comments are not
permitted. Readers are requested to notify
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
of any violations. The editor holds the right to remove any statements that, in the editors opinion, infringe the above guideline(s). The author receives a notification of this action.
