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

event-queue/README.md

@@ -1,13 +1,15 @@
 ---
-title: Event Queue
+title: "Event Queue Pattern in Java: Managing Concurrent Events Efficiently"
+shortTitle: Event Queue
+description: "Learn about the Event Queue design pattern in Java. Discover its best practices, examples, and how to implement it effectively in your Java projects."
 category: Concurrency
 language: en
 tag:
-    - Asynchronous
-    - Decoupling
-    - Messaging
-    - Event-driven
-    - Scalability
+  - Asynchronous
+  - Decoupling
+  - Messaging
+  - Event-driven
+  - Scalability
 ---
 
 ## Also known as
@@ -15,11 +17,11 @@ tag:
 * Event Stream
 * Message Queue
 
-## Intent
+## Intent of Event Queue Design Pattern
 
-The Event Queue pattern is designed to manage tasks in an asynchronous manner, allowing applications to handle operations without blocking user interactions or other processes.
+The Event Queue pattern is designed to manage tasks in an asynchronous manner, allowing applications to handle operations without blocking user interactions or other processes. This improves scalability and system performance.
 
-## Explanation
+## Detailed Explanation of Event Queue Pattern with Real-World Examples
 
 Real-world example
 
@@ -27,13 +29,13 @@ Real-world example
 
 In plain words
 
-> The buffer between sender and receiver improves maintainability and scalability of a system. Event queues are typically used to organise and carry out interprocess communication (IPC).
+> The buffer between sender and receiver improves maintainability and scalability of a system. Event queues are typically used to organize and carry out interprocess communication (IPC).
 
 Wikipedia says
 
 > Message queues (also known as event queues) implement an asynchronous communication pattern between two or more processes/threads whereby the sending and receiving party do not need to interact with the queue at the same time.
 
-**Programmatic Example**
+## Programmatic Example of Event Queue Pattern in Java
 
 This example demonstrates an application using an event queue system to handle audio playback asynchronously.
 
@@ -133,7 +135,7 @@ public void playSound(AudioInputStream stream, float volume) {
 }
 ```
 
-## Applicability
+## When to Use the Event Queue Pattern in Java
 
 This pattern is applicable in scenarios where tasks can be handled asynchronously outside the main application flow, such as in GUI applications, server-side event handling, or in systems that require task scheduling without immediate execution. In particular:
 
@@ -142,13 +144,13 @@ This pattern is applicable in scenarios where tasks can be handled asynchronousl
 * You want to process events asynchronously.
 * You have a limited accessibility resource and the asynchronous process is acceptable to reach that.
 
-## Known Uses
+## Real-World Applications of Event Queue Pattern in Java
 
 * Event-driven architectures
 * GUI frameworks in Java (such as Swing and JavaFX)
 * Server applications handling requests asynchronously
 
-## Consequences
+## Benefits and Trade-offs of Event Queue Pattern
 
 Benefits:
 
@@ -161,14 +163,15 @@ Trade-offs:
 * Complexity in managing the event queue.
 * Potential for difficult-to-track bugs due to asynchronous behavior.
 * Overhead of maintaining event queue integrity and performance.
+* As the event queue model decouples the sender-receiver relationship - this means that the event-queue design pattern is unsuitable for scenarios in which the sender requires a response. For example, this is a prominent feature within online multiplayer games, therefore, this approach requires thorough consideration.
 
-## Related Patterns
+## Related Java Design Patterns
 
 * [Command](https://java-design-patterns.com/patterns/command/) (for encapsulating request processing in a command object)
 * [Observer](https://java-design-patterns.com/patterns/observer/) (for subscribing and notifying changes to multiple observers)
 * [Reactor](https://java-design-patterns.com/patterns/reactor/) (handles requests in a non-blocking event-driven manner similar to Event Queue)
 
-## Credits
+## References and Credits
 
 * [Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions](https://amzn.to/3xzSlC2)
 * [Game Programming Patterns](https://amzn.to/3K96fOn)