TOPIC: SOA
SOA is a common theme in IT and is likely to become even more common.
On this page we will address some frequency asked questions about SOA:
- What does SOA stand for?
- What is SOA?
- What does SOA consist of?
- What are the advantages of SOA?
- Is SOA something new?
- Which terms play a role in SOA?
- What is an ESB?
- Sogeti and SOA
- More questions?
What does SOA stand for?
SOA is an acronym for Service Oriented Architecture.
What is SOA?
SOA is an architecture that applies a number of principles; guidelines and standards for classifying processes into components. This allows us the opportunity to consider data flows at a higher level of abstraction without having to be concerned about the “technical” details. These “technical” details are continuously standardized using supporting commodities. (commoditization). By using this higher level of abstraction, business and IT can use the same model and speak the same language (Business-ICT alignment).
What does SOA consist of?
SOA consists of services: interface vs implementation.
A service executes a defined amount of work and there is a clear agreement as to how the service can and must be used. A characteristic of a service is that based on the exterior it is not obvious what the interior is doing: separation of interface and implementation. For instance, a service can run on a mainframe/COBOL and can be used in the same manner with a JAVA based technology.
What are the advantages of SOA?
The expected advantages of SOA are dynamics; integration and renovation.
Dynamics: by using standards; service reuse; separation of interface and integration; quality resources for realization and use, SOA promises an IT environment that can respond swiftly to changes coming from the business. The ultimate goal of having the business directly modifying business processes and rules in the supporting systems draws ever closer with SOA.
From a business perspective this means faster time-to-market; quicker response resulting in IT no longer being seen as a bottleneck but rather as an enabler etc.
Integration: the integration between different systems or even different organizations is facilitated by the fact that SOA offers uniformity across platforms; is largely based on XML and therefore easily transforms data from different sources.
From the business perspective, this translates into a uniform customer picture; straight though processing; third party integration; channel access; future proofing with respect to laws and rules; mergers and acquisitions etc.
Renovation: The separation of interface and integration gives the ability to access existing systems using services and then to possibly renovate at a later date while maintaining the existing interface. As long as the interface remains the same, the systems can be be migrated; ported or completely revised without the environment suffering.
From the business perspective, this means that legacy systems can be reused; low risk phasing out of expensive platforms and data; lower support costs and better visibility of processen and systems.
Is SOA something new?
SOA isn’t completely new. Like most solutions in IT it is built on previous developments. Component Based Development; Object Orientation and internet developments form some of the roots of SOA. SOA did arrive at precisely the right time: many trends came together and from the business there were many reasons to take a closern look at SOA.
The latest aspects, in as much as that can be said, are:
Openness: Never before were there so many developments that allowed packages and resources to be made open in a uniform manner. Services from Oracle; SAP; Microsoft; IBM etc. kan all be used interchangably.
Standardization: Consequently there has never before been so much discussion about standards. SOA has become the de facto standard architecture. Something that previously seemed impossible, is now a reality: IT is moving toward a worldwide standardization of systems.
Thinking architecturally: There is now for the first time a framework within which from the architect to the software engineer can operate. More than ever before, there are now direct links between IT and business drivers.
Which terms play a role in SOA?
The term SOA is still pretty vague: most suppliers attempt to relate their products to “SOA” . Some of the terms customers often link to SOA are: ESB; Process Integration; Webservices; Granularity; BPEL (Business Process Execution Language); UDDI; WSDL; MQ; Netweaver; XBRL; EAI (Enterprise Application Integration); Event driven architecture etc. Would you like more information about these terms? Please see below: Contact information.
What is an ESB?
An Enterprise Service Bus can be a component of a Service Oriented Architecture. An ESB ensures that services can communicate with each other (“transport”). Additionally, an ESB can manage a number of generic services: transformation of messages; security; management; orchestration (the access of different services in series in the correct order) etc. There are a number of products on the market that provide ESB functionality: Microsoft BizTalk; IBM MQ; Sonic ESB; Tibco; Cordys; Orade Fusion Middleware etc.
A SOA is not a product and cannot be bought as such.
Sogeti and SOA
SOA is an architecture that is clear; practical and conceptually strong. The implementation can take place in phases. In order to get the maximum benefit, it needs to be approached properly: Implementing SOA or architecture (processes) in general still causes lots of headaches. Sogeti can assist customers by: making realistic plans; defining realistic benefits and help prevent pitfalls.
Additionally, SOA touches many layers in an organization. Sogeti offers support at all those levels: from architecture and governance to technical implementation and access to legacy (data). In other words we can help define the vision and the plans in addition to the actual implementation.
Based on our Sogeti–wide view of SOA, that is built on practical experience at almost all of our customers. Architects at these customers have actively participated in the definition of the vision and the validation thereof. This allows us to respond to the most important question in the market: offer assistance based on concrete experience. Rightly so: Realism in IT. For more information about Sogeti and SOA, see the flyers: “SOA and Sogeti” and “Realizing SOA”.
More questions?
If you have additional questions or would like to know more about SOA in general and what Sogeti has to offer in this area, please feel free to contact us:
Erik van Ommeren or Martin van den Berg
