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

partial-response/README.md

@@ -1,15 +1,17 @@
 ---
-title: Partial Response
+title: "Partial Response Pattern in Java: Optimizing Data Delivery for Efficient Web Services"
+shortTitle: Partial Response
+description: "Explore the Partial Response design pattern for APIs, a strategy to boost performance by allowing clients to process data as soon as it becomes available. Learn how it improves scalability and reduces server load."
 category: Behavioral
 language: en
 tag:
-    - API design
-    - Asynchronous
-    - Client-server
-    - Decoupling
-    - Performance
-    - Scalability
-    - Web development
+  - API design
+  - Asynchronous
+  - Client-server
+  - Decoupling
+  - Performance
+  - Scalability
+  - Web development
 ---
 
 ## Also known as
@@ -17,11 +19,11 @@ tag:
 * Incremental Response
 * Partial Result
 
-## Intent
+## Intent of Partial Response Design Pattern
 
 To enable an application to return a partial response to a client, improving perceived performance and enabling the client to start processing parts of the data before the entire response is available.
 
-## Explanation
+## Detailed Explanation of Partial Response Pattern with Real-World Examples
 
 Real-world example
 
@@ -31,7 +33,7 @@ In plain words
 
 > The Partial Response design pattern allows a system to send portions of data to the client as they become available, enabling the client to start processing the data before the complete response is received.
 
-**Programmatic Example**
+## Programmatic Example of Partial Response Pattern in Java
 
 The Partial Response design pattern allows clients to specify which fields of a resource they need. This pattern is useful for reducing the amount of data transferred over the network and allowing clients to start processing data sooner.
 
@@ -136,21 +138,23 @@ To summarize, in this example:
 
 By implementing the Partial Response design pattern, clients can request only the necessary data, enhancing performance and reducing bandwidth usage.
 
-## Applicability
+## When to Use the Partial Response Pattern in Java
 
 Use the Partial Response pattern when
 
-* When the response data is large or takes a long time to process and transfer.
+* Utilize the Partial Response pattern when dealing with large data sets or APIs that require improved load time and performance.
 * When it’s beneficial for the client to begin processing the data as it arrives rather than waiting for the complete response.
 * In APIs where different clients might need different subsets of data, allowing them to specify what they need.
 
-## Known Uses
+## Real-World Applications of Partial Response Pattern in Java
+
+This pattern is widely adopted in
 
 * RESTful APIs allowing clients to specify fields they want using query parameters.
 * Streaming large datasets where initial parts of the data can be sent immediately (e.g., video streaming).
 * GraphQL queries where clients can request only specific fields to be returned.
 
-## Consequences
+## Benefits and Trade-offs of Partial Response Pattern
 
 Benefits:
 
@@ -164,13 +168,13 @@ Trade-offs:
 * Error Handling: May complicate error handling and recovery if only parts of the data are received correctly.
 * State Management: Requires careful management of state, especially if the partial responses are to be processed incrementally.
 
-## Related Patterns
+## Related Java Design Patterns
 
 * Asynchronous Messaging: Often used together with asynchronous messaging patterns to handle partial responses without blocking the client.
 * [Caching](https://java-design-patterns.com/patterns/caching/): Can be combined with caching patterns to store partial responses and avoid redundant data transfers.
 * [Proxy](https://java-design-patterns.com/patterns/proxy/): The proxy can intercept requests and manage partial responses, providing a buffer between the client and server.
 
-## Credits
+## References and Credits
 
 * [Building Microservices](https://amzn.to/3UACtrU)
 * [Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems](https://amzn.to/4dKEwBa)