| |
| Data Services Layer and Its Role in SOA: Principles, Boundaries, Contexts and Possibilities |
 |
Speaker:
Dr. Mark Davydov
Director of Systems Development
CareFirst Blue Cross Blue Shield
Track:
DataServices World
|
 |
 |
 |
The ever-increasing movement towards implementing complex SOA-based applications has triggered a direct attention of leading industry researchers and practitioners to the subject of layering in such applications, in general, and the relationship between the fields of database engineering and SOA, in particular. Common notion of interoperability, loose-coupling between consumers and providers, and complexity-hiding, and demands for enabling extensive reuse of application services to address unforeseen business requirements for new user types, for new types of information and for new composite views has brought to the forefront the concept of Data Services Layer (DSL) as a distinct architectural layer. DSL is an essential part of an application architecture that combines data access functions and corresponding database structures and promises ensuring the next harvest for SOA ROI.
This presentation thoroughly examines the concept of DSL from an architectural and development perspective to reveal significant principles, context, and interrelationships that, in turn, allows focusing on patterns, best practices, design strategies, and proven solutions using the key technologies including semantic models of XML data, XQuery, and popularized SOA-driven commercial and open source database implementations that moved aggressively toward explicit support of SOA, for example, Microsoft SQL Server 2005, IBM DB2 Viper, XAware Open Source 5, and Apache Tuscany.
|
| |
| |
| LINQ, Entity Framework and ADO.NET Entity Framework and Data Services for the Web |
 |
Speaker:
Mike Pizzo
Principal Architect
Microsoft
Track:
DataServices World
|
 |
 |
 |
The new wave of Web applications are built on technologies such as AJAX and Microsoft Silverlight, which enable developers to build better, richer user experiences. These technologies bring a shift in how applications are organized, including a stronger separation of presentation from data. Technologies such as Language Integrated Query (LINQ) and ADO.NET Entity Framework and Data Services simplify the job of developers.
The ADO.NET Entity Framework raises the level of abstraction for data programming. It is the evolution of ADO.NET that allows developers to program in terms of the standard ADO.NET abstraction or in terms of persistent objects
(ORM) and is built upon the standard ADO.NET Provider model. The Entity Framework introduces a set of services around the Entity Data Model (EDM) (a medium for defining domain models for an application).
The goal of ADO.NET Data Services is to enable applications to expose data as a REST-based data service that can be consumed by Web clients within a corporate network and across the Internet. The data service is reachable over HTTP, and URIs are used to identify the various pieces of information available through the service. Interactions with the data service happens in terms of HTTP verbs, such as GET, POST, PUT, and DELETE, and the data exchanged in those interactions is represented in simple formats, such as AtomPub and JavaScript Object Notation (JSON).
|
| |
|