Have you ever thought about making a Domain Model for your SOA-Architecture that lines up with your meta data model? No? Here is a good White Paper from BEA. Go ahead and check it out.
SOA Domain Model White Paper
Tuesday, April 25, 2006
Sunday, April 23, 2006
What is a Service?
This is a questions I hear very often - not only from the Management but also from Architects and Developers.
Let's try to find an answer....
First, you should understand the Term 'Service' because this is the most important part of any Service Oriented Architecture.
The term 'Service' indicates that IT is moving towards the Business Layers and therefore offering its functions as Services.
A Service has the following characteristics:
Let's try to find an answer....
First, you should understand the Term 'Service' because this is the most important part of any Service Oriented Architecture.
The term 'Service' indicates that IT is moving towards the Business Layers and therefore offering its functions as Services.
A Service has the following characteristics:
- a Service is, from a business perspective, a reusable component
- a Service has a standardized interface that abstracts the implementation details and technology of the underlying system. It is therefore loosly coupled.
- a Service always has a contracts that specifies the terms of use and the policies applied.
To make it more clear what Services are we can differentiate between three types of Services:
- Business Services; offer a Business Functionality that is needed in a certain Business Process Step.
- Intermediary Services; handle technology gaps, offer routing, transformation and security capabilities.
- Basic Services; implement the needed Business Logic and handle the data.
Service Repository
Managing Services will be as managing any other asset within your company. Therefore you might need a COTS-Products that assists you in doing that.
There are - besides the also very good and performant Gnu-Software such as JUDDI - two main products available.
There are - besides the also very good and performant Gnu-Software such as JUDDI - two main products available.
From a architecture point of view the Infravion X-Registry is much more sophisticated since its architecture is highly component based. Neverless the distribution of the functions and the underlying different data bases (1 for registry, 1 for repository) are completely transparent to the user. Hence, the user does not have to care whether he want's to use a function of the registry or the repository. It's just all there right at your fingertips.
The advantages of the COTS-Products compared to Gnu-Software (e.g. JUDDI) are in fact that you will get not only a registry (UDDI) but also a repository (eb).
Subscribe to:
Posts (Atom)
