Data access object: Difference between revisions

Revision as of 16:01, 4 December 2022

Revision as of 20:11, 10 February 2023

Line 1:

{{About|the software design pattern|the Microsoft library|Jet Data Access Objects}}

In [[Software|software]], a '''data access object''' ('''DAO''') is a pattern that provides an abstract [[Interface (computer science)|interface]] to some type of [[database]] or other [[Persistence (computer science)|persistence mechanism]]. By mapping application calls to the persistence layer, the DAO provides data operations without exposing database details. This isolation supports the [[single responsibility principle]]. It separates the data access the application needs, in terms of ___domain-specific objects and data types (the DAO's public interface), from how these needs can be satisfied with a specific [[Database Management System|DBMS]] (the implementation of the DAO).

Although this [[design pattern]] is applicable to most programming languages, most software with persistence needs, and most databases, it is traditionally associated with [[Java Platform, Enterprise Edition|Java EE]] applications and with [[relational databases]] (accessed via the [[JDBC]] API because of its origin in [[Sun Microsystems]]' best practice guidelines<ref>