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

composite-entity/README.md

@@ -1,40 +1,42 @@
 ---
-title: Composite Entity
+title: "Composite Entity Pattern in Java: Streamlining Persistent Object Management"
+shortTitle: Composite Entity
+description: "Learn about the Composite Entity design pattern in Java, a structural pattern used to manage interrelated persistent objects as a single entity. Ideal for enterprise applications and EJB, this pattern simplifies complex data structures and client interactions."
 category: Structural
 language: en
 tag:
-    - Client-server
-    - Data access
-    - Decoupling
-    - Enterprise patterns
-    - Object composition
-    - Persistence
-    - Resource management
+  - Client-server
+  - Data access
+  - Decoupling
+  - Enterprise patterns
+  - Object composition
+  - Persistence
+  - Resource management
 ---
 
 ## Also known as
 
 * Coarse-Grained Entity
 
-## Intent
+## Intent of Composite Entity Design Pattern
 
-The Composite Entity design pattern is aimed at managing a set of interrelated persistent objects as if they were a single entity. It is commonly used in the context of Enterprise JavaBeans (EJB) and similar enterprise frameworks to represent graph-based data structures within business models, enabling clients to treat them as a single unit.
+The Composite Entity design pattern in Java is aimed at managing a set of interrelated persistent objects as if they were a single entity. It is commonly used in enterprise applications, particularly within the context of Enterprise JavaBeans (EJB) and similar enterprise frameworks, to represent graph-based data structures within business models. This pattern enables clients to treat these complex structures as a single unit, simplifying operations and interactions.
 
-## Explanation
+## Detailed Explanation of Composite Entity Pattern with Real-World Examples
 
 Real-world example
 
-> Consider a university registration system where a "Student" entity is a composite entity. Each "Student" object includes several dependent objects: personal details, course enrollments, grades, and payment information. Instead of managing each of these aspects separately, the Composite Entity pattern allows the university system to treat the "Student" as a single entity. This simplifies operations such as enrolling a student in a new course, updating grades, and processing payments, since all related actions can be managed through the composite "Student" object.
+> Consider a university registration system where a "Student" entity is a composite entity. Each "Student" object includes several dependent objects: personal details, course enrollments, grades, and payment information. Instead of managing each of these aspects separately, the Composite Entity design pattern allows the university system to treat the "Student" as a single entity. This simplifies operations such as enrolling a student in a new course, updating grades, and processing payments, since all related actions can be managed through the composite "Student" object.
 
 In plain words
 
-> Composite entity pattern allows a set of related objects to be represented and managed by a unified object.
+> The Composite Entity pattern in Java allows a set of related persistent objects to be represented and managed by a unified object, simplifying enterprise application design.
 
 Wikipedia says
 
 > Composite entity is a Java EE Software design pattern and it is used to model, represent, and manage a set of interrelated persistent objects rather than representing them as individual fine-grained entity beans, and also a composite entity bean represents a graph of objects.
 
-**Programmatic Example**
+## Programmatic Example of Composite Entity in Java
 
 For a console, there may be many interfaces that need to be managed and controlled. Using the composite entity pattern, dependent objects such as messages and signals can be combined and controlled using a single object.
 
@@ -123,25 +125,26 @@ public App(String message, String signal) {
 }
 ```
 
-## Applicability
+## When to Use the Composite Entity Pattern in Java
 
-* Useful in enterprise applications where business objects are complex and involve various interdependent objects.
+* Useful in Java enterprise applications where business objects are complex and involve various interdependent persistent objects.
 * Ideal for scenarios where clients need to work with a unified interface to a set of objects rather than individual entities.
 * Applicable in systems that require a simplified view of a complex data model for external clients or services.
 
-## Known Uses
+
+## Real-World Applications of Composite Entity Pattern in Java
 
 * Enterprise applications with complex business models, particularly those using EJB or similar enterprise frameworks.
 * Systems requiring abstraction over complex database schemas to simplify client interactions.
-* Applications that need to enforce consistency or transactions across multiple objects in a business entity.
+* Applications that need to enforce consistency or transactions across multiple persistent objects in a business entity.
 
-## Consequences
+## Benefits and Trade-offs of Composite Entity Pattern
 
 Benefits:
 
 * Simplifies client interactions with complex entity models by providing a unified interface.
 * Enhances reusability and maintainability of the business layer by decoupling client code from the complex internals of business entities.
-* Facilitates easier transaction management and consistency enforcement across a set of related objects.
+* Facilitates easier transaction management and consistency enforcement across a set of related persistent objects.
 
 Trade-offs:
 
@@ -149,13 +152,13 @@ Trade-offs:
 * Can lead to overly coarse-grained interfaces that might not be as flexible for all client needs.
 * Requires careful design to avoid bloated composite entities that are difficult to manage.
 
-## Related Patterns
+## Related Java Design Patterns
 
 * [Decorator](https://java-design-patterns.com/patterns/decorator/): For dynamically adding behavior to individual objects within the composite entity without affecting the structure.
 * [Facade](https://java-design-patterns.com/patterns/facade/): Provides a simplified interface to a complex subsystem, similar to how a composite entity simplifies access to a set of objects.
 * [Flyweight](https://java-design-patterns.com/patterns/flyweight/): Useful for managing shared objects within a composite entity to reduce memory footprint.
 
-## Credits
+## References and Credits
 
 * [Core J2EE Patterns: Best Practices and Design Strategies](https://amzn.to/4cAbDap)
 * [Enterprise Patterns and MDA: Building Better Software with Archetype Patterns and UML](https://amzn.to/49mslqS)