Data access layer: Difference between revisions

Revision as of 03:43, 26 October 2009

Revision as of 03:44, 26 October 2009

Line 1:

{{Unreferenced|date=May 2008}}

A '''Data Access Layer''' (DAL) is a [[layer (object-oriented design)|layer]] of a [[computer program]] which provides simplified [[access]] to [[data]] stored in [[persistent storage]] of some kind, such as an [[entity relationship|entity-relational]] [[database]].

This data access layer is used in turn by other program modules to access and manipulate the data within the data store without having to deal with the complexities inherent in this access.

For example, the DAL might return a reference to an [[object (computer science)|object]] (in terms of [[object-oriented programming]]) complete with its attributes instead of a [[row]] of [[Field (computer science)|fields]] from a database [[table (database)|table]]. This allows the client (or user) modules to be created with a higher level of [[abstraction]]. This kind of model could be implemented by creating a class of data access methods that directly reference a corresponding set of database stored procedures. Another implementation could potentially retrieve or write records to or from a file system. The DAL hides this complexity of the underlying data store from the external world.

For example, instead of using commands such as ''insert'', ''delete'', and ''update'' to access a specific table in a database, a class and a few stored procedures could be created in the database. The procedures would be called from a method inside the class, which would return an object containing the requested values. Or, the insert, delete and update commands could be executed within simple functions like ''registeruser'' or ''loginuser'' stored within the data access layer.

Also, business logic methods from an application can be mapped to the Data Access Layer. So, for example, instead of making a query into a database to fetch all users from several tables the application can call a single method from a DAL which abstracts those database calls.

Applications using a data access layer can be either database server dependent or independent. If the data access layer supports multiple database types, the application becomes able to use whatever databases the DAL can talk to. In either circumstance, having a data access layer provides a centralized ___location for all calls into the database, and thus makes it easier to port the application to other database systems (assuming that 100% of the database interaction is done in the DAL for a given application).

[[Object-Relational Mapping]] tools provide data layers in this fashion, following the [[Active record pattern|active record]] model. The ORM/active-record model is popular with web frameworks, but it has not been proven to be better than a straightforward approach of implementing a collection of ___domain-specific data access functions.

== See also ==

* [[Data Access Object]]

[[Category:Databases]]

{{database-stub}}