Service-oriented Architecture (SOA)
The term "service-oriented architecture"/SOA is heard everywhere. Even the press in the information and telecommunications sector is currently discussing this topic very intensively. In an attempt to present one option to approach the topic, we go into questions such as: "What is SOA?", "When can SOA be used?" and "What benefits does SOA bring in the long-term?".
Service-oriented Architecture - explained
SOA generally describes a software infrastructure in which software modules are organised as services which can be used by other systems via the network. Monolithic structures such as those applied at the end of the 1990s no longer adequately meet the present day requirements because, in particular monolithic structures, encounter problems when it comes to integrating a number of heterogeneous systems. And this is where SOA comes in. As SOA is based on existing business processes via a so-called "Service Orchestration", IT can be more easily oriented to the current business world.
Services, which are offered by a SOA and used by other systems are subject to strict rules. Contracts determine which messages the services accept, how these have to be formatted etc. This does not relate to the actual implementation, it merely describes the services in a declarative manner. What does one hope to gain from this? Better inter-operability of the widely differing services which are made available on different platforms such as Microsoft .NET or J2EE.
Loose coupling for greater availability and reliable messaging
WebServices form the bases for Service-oriented Architecture. They constitute the interface of all services and accept the messages previously stipulated per contract. Via the message-based channels it is possible to establish loose connections between the systems. The need to wait for a reply is avoided. What the service does with this message is not revealed to the accessing system. We therefore depart from the prevailing opinion and fact often encountered in reality, that WebServices are nothing else but Remote Procedure Calls which are upgraded with a little XML.
Advantages and benefits
The SOA concept is beneficial to the extent that it is modelled on the level of business processes and therefore facilitates the maintenance of existing systems and the implementation of new services. Technical details are no long of such importance to the planning of services that they could become a show-stopper for the launch of a new service or the modification of an existing one. Naturally there will still have to be a team in the future which implements the services but communications with existing participants in the SOA structure will be significantly simpler and easier to plan.
swift.consult also regards Service-oriented Architecture as a step in the right direction and is convinced that this architecture form will be of great significance in the future, gradually replacing other structures. Have we aroused your interest or would you like to discuss this topic with us? Don't hesitate to contact us. We are looking forward to hearing your ideas, suggestions and questions.
Further information
Service-oriented Architecture - an Introduction under O'Reillys xml.com
Lab
learn more