In corporations, most of business applications have to deal with different data representations, when you start exposing these applications as services in a SOA environment, there is still a need to handle data one way or another. Handling Data becomes a bigger problem when you have to deal with multiple and different sources of data, and most of the solutions today is only able to treat on type of data, if your service is using Hibernate or other frameworks, to access a relational database, you would have to re-implement the service to access data from a XML source.
Tuscany Data Access Service (a.k.a DAS) comes handy to solve this problem, it's intended to be a Universal API capable to handle various data sources. The beauty of this is that, if your application needs to handle data from a relational database, XML, etc you would use the same API while building your SOA services.
Well, now imagine if you could define all the data access information while defining your service contract and then all the necessary code to handle access to data in these differences data sources would be handled internally by you ? This is what we are trying to accomplish with Declarative DAS in Apache Tuscany.
This is going to be possible be a tight integration between Tuscany DAS and Tuscany SCA creating the infrastructure to make all this possible and making your service development experience much simpler.
Here is a draft diagram to help you visualize the building blocks for Declarative DAS:
Declarative DAS : Extend the SCA programming model to expose services that interact with a persistent layer in a declarative fashion hiding the implementation details from the service developer.It’s all about simplicity, allowing a service to be defined without explicitly coding the persistence layer.
Liked the vision ? read more about Declarative DAS from the archives of Tuscany-dev mailing list.
Want to help us, learn more how to get involved.
0 comments:
Post a Comment