Share to: share facebook share twitter share wa share telegram print page

Data access object

This article is about the software design pattern. For the Microsoft library, see Jet Data Access Objects.

In software, a data access object (DAO) is a pattern that provides an abstract interface to some type of database or other 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 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 EE applications and with relational databases (accessed via the JDBC API because of its origin in Sun Microsystems' best practice guidelines[1] "Core J2EE Patterns".

This object can be found in the Data Access layer of the 3-Tier Architecture.

There are various ways in which this object can be implemented:

  • One DAO for each table.
  • One DAO for all the tables for a particular DBMS.
  • Where the SELECT query is limited only to its target table and cannot incorporate JOINS, UNIONS, subqueries and Common Table Expressions (CTEs)
  • Where the SELECT query can contain anything that the DBMS allows.

Advantages

Using data access objects (DAOs) offers a clear advantage: it separates two parts of an application that don't need to know about each other. This separation allows them to evolve independently. If business logic changes, it can rely on a consistent DAO interface. Meanwhile, modifications to persistence logic won't affect DAO clients.[2][3]

All details of storage are hidden from the rest of the application (see information hiding). Unit testing code is facilitated by substituting a test double for the DAO in the test, thereby making the tests independent of the persistence layer.

In the context of the Java programming language, DAO can be implemented in various ways. This can range from a fairly simple interface that separates data access from the application logic, to frameworks and commercial products.

Technologies like Java Persistence API and Enterprise JavaBeans come built into application servers and can be used in applications that use a Java EE application server. Commercial products such as TopLink are available based on object–relational mapping (ORM). Popular open source ORM software includes Doctrine, Hibernate, iBATIS and JPA implementations such as Apache OpenJPA.[4]

Disadvantages

Potential disadvantages of using DAO include leaky abstraction,[citation needed] code duplication, and abstraction inversion. In particular, the abstraction of the DAO as a regular Java object can obscure the high cost of each database access. Developers may inadvertently make multiple database queries to retrieve information that could be returned in a single operation. If an application requires multiple DAOs, the same create, read, update, and delete code may have to be written for each DAO.[5]

Note that these disadvantages only appear when you have a separate DAO for each table and the SELECT query is prevented from accessing anything other than the target table.

Tools and frameworks

See also

References

  1. ^ "Core J2EE Patterns - Data Access Objects". Sun Microsystems Inc. 2007-08-02.
  2. ^ "Data Access Object(DAO) Design Pattern". DigitalOcean. 2022-08-03. Retrieved 2024-07-08.
  3. ^ "Data Access Object(DAO) Design Pattern". GeeksforGeeks. 2017-08-26. Retrieved 2024-07-08.
  4. ^ "Data Access Object(DAO) Design Pattern". GeeksforGeeks. 2017-08-26. Retrieved 2024-01-29.
  5. ^ See http://www.ibm.com/developerworks/java/library/j-genericdao/index.html for workarounds
  6. ^ Hodgson, Kyle; Reid, Darren (2015-01-23). ServiceStack 4 Cookbook. Packt Publishing Ltd. p. Chapter 4. ISBN 9781783986576. Retrieved 22 June 2016.
Kembali kehalaman sebelumnya