Designing and Developing SOA based application
Let's start at the beginning : What is SOA ?
The question may sound stupid, but try to answer by yourself to this question, and then ask it around your friends and colleagues : I'm pretty sure that you will not get a formal and unique response to it ... unless they are Dutch (*) ... ;)
From a very high level, we can summarize SOA as an application design architecture which allows to move away from a monolithic/silo-based application model, to a services oriented, highly reuseable, implementation regardless and loosely-coupled based composite-application model.
In theory, this sounds idyllic. But if we drill-down a bit further we realized that a lot of areas still need clarification. For example : How to create those "services" ? Should I have to write them again or is there any technique to "wrap" existing modules from my legacy applications to "services" ? How to link and orchestrate those services together ? How to secure efficiently the communication between services ?
Introducing Service Component Architecture (SCA) and Service Data Objects (SDO)
The question may sound stupid, but try to answer by yourself to this question, and then ask it around your friends and colleagues : I'm pretty sure that you will not get a formal and unique response to it ... unless they are Dutch (*) ... ;)
From a very high level, we can summarize SOA as an application design architecture which allows to move away from a monolithic/silo-based application model, to a services oriented, highly reuseable, implementation regardless and loosely-coupled based composite-application model.
In theory, this sounds idyllic. But if we drill-down a bit further we realized that a lot of areas still need clarification. For example : How to create those "services" ? Should I have to write them again or is there any technique to "wrap" existing modules from my legacy applications to "services" ? How to link and orchestrate those services together ? How to secure efficiently the communication between services ?
Introducing Service Component Architecture (SCA) and Service Data Objects (SDO)
Recently, Oracle and other major SOA vendors have released 2 new specifications, Service Component Architecture (SCA) and Service Data Objects (SDO), which aim to :
- Help developers and architects to build SOA based system in the common way, by reducing the design and development complexity, as well as eliminating dependencies to the middleware where those component are executed.
- A standard way to represent business data to developers and architects, regardless on how they are physicall accessed.
More information can be found at the Oracle Service-Oriented Architecture Technology Center within the Oracle Technology Network website (http://otn.oracle.com).
In the future, I'll drill down into a specific area about securing and managing web services : Policy Driven Approach to secure SOA environment. So stay tune !
* SOA in Dutch stands for Seksueel Overdraagbare Aandoeningen, which means Sexually Transmitted Diseases ...
posted by Manh-Kiet Yap at
3:19 PM
|
1 comments
