docs: Content SEO updates (#2990)

* update yaml frontmatter format

* update abstract document

* update abstract factory

* use the new pattern template

* acyclic visitor seo

* adapter seo

* ambassador seo

* acl seo

* aaa seo

* async method invocation seo

* balking seo

* bridge seo

* builder seo

* business delegate and bytecode seo

* caching seo

* callback seo

* chain seo

* update headings

* circuit breaker seo

* client session + collecting parameter seo

* collection pipeline seo

* combinator SEO

* command seo

* cqrs seo

* commander seo

* component seo

* composite seo

* composite entity seo

* composite view seo

* context object seo

* converter seo

* crtp seo

* currying seo

* dao seo

* data bus seo

* data locality seo

* data mapper seo

* dto seo

* decorator seo

* delegation seo

* di seo

* dirty flag seo

* domain model seo

* double buffer seo

* double checked locking seo

* double dispatch seo

* dynamic proxy seo

* event aggregator seo

* event-based asynchronous seo

* eda seo

* event queue seo

* event sourcing seo

* execute around seo

* extension objects seo

* facade seo

* factory seo

* factory kit seo

* factory method seo

* fanout/fanin seo

* feature toggle seo

* filterer seo

* fluent interface seo

* flux seo

* flyweight seo

* front controller seo

* function composition seo

* game loop seo

* gateway seo

* guarded suspension seo

* half-sync/half-async seo

* health check seo

* hexagonal seo

* identity map seo

* intercepting filter seo

* interpreter seo

* iterator seo

* layers seo

* lazy loading seo

* leader election seo

* leader/followers seo

* lockable object seo

* rename and add seo for marker interface

* master-worker seo

* mediator seo

* memento seo

* metadata mapping seo

* microservice aggregator seo

* api gw seo

* microservices log aggregration seo

* mvc seo

* mvi seo

* mvp seo

* mvvm seo

* monad seo

* monitor seo

* monostate seo

* multiton seo

* mute idiom seo

* naked objects & notification seo

* null object seo

* object mother seo

* object pool seo

* observer seo

* optimistic locking seo

* page controller seo

* page object seo

* parameter object seo

* partial response seo

* pipeline seo

* poison pill seo

* presentation model seo

* private class data seo

* producer-consumer seo

* promise seo

* property seo

* prototype seo

* proxy seo

* queue-based load leveling seo

* reactor seo

* registry seo

* repository seo

* RAII seo

* retry seo

* role object seo

* saga seo

* separated interface seo

* serialized entity seo

* serialized lob seo

* servant seo

* server session seo

* service layer seo

* service locator seo

* service to worker seo

* sharding seo

* single table inheritance seo

* singleton seo

* spatial partition seo

* special case seo

* specification seo

* state seo

* step builder seo

* strangler seo

* strategy seo

* subclass sandbox seo

* table module seo

* template method seo

* throttling seo

* tolerant reader seo

* trampoline seo

* transaction script seo

* twin seo

* type object seo

* unit of work seo

* update method seo

* value object seo

* version number seo

* virtual proxy seo

* visitor seo

* seo enhancements

* seo improvements

* SEO enhancements

* SEO improvements

* SEO additions

* SEO improvements

* more SEO improvements

* rename hexagonal + SEO improvements

* SEO improvements

* more SEO stuff

* SEO improvements

* SEO optimizations

* SEO enhancements

* enchance SEO

* improve SEO

* SEO improvements

* update headers

data-access-object/README.md

@@ -1,14 +1,16 @@
 ---
-title: Data Access Object
+title: "Data Access Object Pattern in Java: Streamlining Database Interaction"
+shortTitle: Data Access Object (DAO)
+description: "Explore the Java Data Access Object (DAO) pattern to effectively separate business logic from database operations. Learn implementation strategies, real-world examples, and best practices."
 category: Structural
 language: en
 tag:
-    - Abstraction
-    - Data access
-    - Data processing
-    - Decoupling
-    - Layered architecture
-    - Persistence
+  - Abstraction
+  - Data access
+  - Data processing
+  - Decoupling
+  - Layered architecture
+  - Persistence
 ---
 
 ## Also known as
@@ -16,11 +18,11 @@ tag:
 * Data Access Layer
 * DAO
 
-## Intent
+## Intent of Data Access Object Design Pattern
 
 The Data Access Object (DAO) design pattern aims to separate the application's business logic from the persistence layer, typically a database or any other storage mechanism. By using DAOs, the application can access and manipulate data without being dependent on the specific database implementation details.
 
-## Explanation
+## Detailed Explanation of Data Access Object Pattern with Real-World Examples
 
 Real-world example
 
@@ -34,7 +36,7 @@ Wikipedia says
 
 > In computer software, a data access object (DAO) is a pattern that provides an abstract interface to some type of database or other persistence mechanism.
 
-**Programmatic Example**
+## Programmatic Example of DAO Pattern in Java
 
 There's a set of customers that need to be persisted to database. Additionally, we need the whole set of CRUD (create/read/update/delete) operations, so we can operate on customers easily.
 
@@ -193,11 +195,11 @@ The program output:
 10:02:09.898 [main] INFO com.iluwatar.dao.App -- customerDao.getAllCustomers(): java.util.stream.ReferencePipeline$Head@f2f2cc1
 ```
 
-## Class diagram
+## Detailed Explanation of Data Access Object Pattern with Real-World Examples
 
 ![Data Access Object](./etc/dao.png "Data Access Object")
 
-## Applicability
+## When to Use the Data Access Object Pattern in Java
 
 Use the Data Access Object in any of the following situations:
 
@@ -205,18 +207,18 @@ Use the Data Access Object in any of the following situations:
 * The application needs to support multiple types of databases or storage mechanisms without significant code changes.
 * You want to keep the database access clean and simple, and separate from business logic.
 
-## Tutorials
+## Data Access Object Pattern Java Tutorials
 
 * [The DAO Pattern in Java(Baeldung)](https://www.baeldung.com/java-dao-pattern)
 * [Data Access Object Pattern (TutorialsPoint)](https://www.tutorialspoint.com/design_pattern/data_access_object_pattern.htm)
 
-## Known Uses
+## Real-World Applications of DAO Pattern in Java
 
 * Enterprise applications that require database interaction.
 * Applications requiring data access to be adaptable to multiple storage types (relational databases, XML files, flat files, etc.).
 * Frameworks providing generic data access functionalities.
 
-## Consequences
+## Benefits and Trade-offs of Data Access Object Pattern
 
 Benefits:
 
@@ -231,14 +233,14 @@ Trade-offs:
 * Overhead: For simple applications, the DAO pattern might introduce more overhead than necessary.
 * Learning Curve: Developers might need time to understand and implement the pattern effectively, especially in complex projects.
 
-## Related Patterns
+## Related Java Design Patterns
 
 * [Abstract Factory](https://java-design-patterns.com/patterns/abstract-factory/): Helps in abstracting the creation of DAOs, especially when supporting multiple databases or storage mechanisms.
 * [Factory](https://java-design-patterns.com/patterns/factory/): Can be used to instantiate DAOs dynamically, providing flexibility in the choice of implementation.
 * [Service Layer](https://java-design-patterns.com/patterns/service-layer/): Often used in conjunction with the DAO pattern to define application's boundaries and its set of available operations.
 * [Strategy](https://java-design-patterns.com/patterns/strategy/): Might be employed to change the data access strategy at runtime, depending on the context.
 
-## Credits
+## References and Credits
 
 * [Core J2EE Patterns: Best Practices and Design Strategies](https://amzn.to/49u3r91)
 * [Expert One-on-One J2EE Design and Development](https://amzn.to/3vK3pfq)