tiennm99/java-design-patterns
1
0
Fork 0
mirror of https://github.com/tiennm99/java-design-patterns.git synced 2026-05-26 00:00:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: updates to several patterns

Browse Source
This commit is contained in:
Ilkka Seppälä
2024-05-28 19:46:39 +03:00
parent 4652842c94
commit 584e949714
70 changed files with 347 additions and 479 deletions
Download Patch File Download Diff File Expand all files Collapse all files
data-access-object/README.md
+1 -1
View File
@@ -22,7 +22,7 @@ The Data Access Object (DAO) design pattern aims to separate the application's b
## Explanation
Real world example
Real-world example
> Imagine a library system where the main application manages book loans, user accounts, and inventory. The Data Access Object (DAO) pattern in this context would be used to separate the database operations (such as fetching book details, updating user records, and checking inventory) from the business logic of managing loans and accounts. For instance, there would be a `BookDAO` class responsible for all database interactions related to books, such as retrieving a book by its ISBN or updating its availability status. This abstraction allows the library system's main application code to focus on business rules and workflows, while the `BookDAO` handles the complex SQL queries and data management. This separation makes the system easier to maintain and test, as changes to the data source or business logic can be managed independently.