Data Services ecology

Data Services in SOA directly relates to several existing technologies and extends them:

• Persistence, known as ORM in the past.


• Integration, connectors to access packaged applications and/or exotic legacy data sources.


• Web Services.

In the middle, between persistence and services you will find SDO, where in the past you knew JDO or JPA.

Between Integration and services, EAI is evolving into ESBs. It is more standardized and relies on XML and Web Services but at the end it is still asynchronous messaging.

To some extent, Data Services are an extension of mapping to services in a disconnected model.

There are some other related technologies:

• Security,


• Management,


• Cache,


• ...

Data Services ecology

Data Services in SOA directly relates to several existing technologies and extends them:

• Persistence, known as ORM in the past.


• Integration, connectors to access packaged applications and/or exotic legacy data sources.


• Web Services.

In the middle, between persistence and services you will find SDO, where in the past you knew JDO or JPA.

Between Integration and services, EAI is evolving into ESBs. It is more standardized and relies on XML and Web Services but at the end it is still asynchronous messaging.

To some extent, Data Services are an extension of mapping to services in a disconnected model.

There are some other related technologies:

• Security,


• Management,


• Cache,


• ...

Data Services duality

Data Services have a dual personality in SOA:

• They can be data providers
  
  
  
  • In that sense they have some specific characteristics, for instance they are mostly transactional and synchronous.
  
  
  
  


• They can be interfaces, for instance a Data Service will publish some data and will allow updates

A DAS for instance is able to aggregate and manipulate data through a Data Service it exposes but at the same time, the same DAS can consume other Data Services and integrate their data.

This is exactly what the Xcalia DAS is doing. It consumes and provides Data Services.

Data Services duality

Data Services have a dual personality in SOA:

• They can be data providers
  
  
  
  • In that sense they have some specific characteristics, for instance they are mostly transactional and synchronous.
  
  
  
  


• They can be interfaces, for instance a Data Service will publish some data and will allow updates

A DAS for instance is able to aggregate and manipulate data through a Data Service it exposes but at the same time, the same DAS can consume other Data Services and integrate their data.

This is exactly what the Xcalia DAS is doing. It consumes and provides Data Services.

Incorporating Enterprise Data into SOA

On November 2006, InfoQ released an interesting article by Boris Lublinsky about Data Access in SOA.

http://www.infoq.com/articles/SOA-enterprise-data

Incorporating Enterprise Data into SOA

On November 2006, InfoQ released an interesting article by Boris Lublinsky about Data Access in SOA.

http://www.infoq.com/articles/SOA-enterprise-data

Enterprise Data Access Layer

Having multiple types of data sources in an enterprise is pure reality.

Having business applications developed in multiple programming languages is evidence, and BPM (workflow, rules, BPEL) also widens that scope.

Managing consistent, fast and reliable data access in such situation is a nightmare.

Unless you plug into our standard driven data access layer.

• You manage and understand better your data sources and your data models


• You give an high level access to all your data


• You benefit from key performance driven features (cache management,...)


• Transaction are fully managed, even when heterogeneous data sources are involved in a single data operation.

Do you need more ?

Ask us !