mirror of
https://github.com/tiennm99/java-design-patterns.git
synced 2026-05-22 00:25:08 +00:00
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
This commit is contained in:
+23
-17
@@ -1,13 +1,15 @@
|
||||
---
|
||||
title: Specification
|
||||
title: "Specification Pattern in Java: Enhancing Business Rules with Decoupled Logic"
|
||||
shortTitle: Specification
|
||||
description: "Dive deep into the Specification design pattern in Java, a strategic solution for encapsulating business rules. Learn how to implement, combine, and apply this pattern effectively in your software development projects."
|
||||
category: Behavioral
|
||||
language: en
|
||||
tag:
|
||||
- Business
|
||||
- Domain
|
||||
- Encapsulation
|
||||
- Enterprise patterns
|
||||
- Extensibility
|
||||
- Business
|
||||
- Domain
|
||||
- Encapsulation
|
||||
- Enterprise patterns
|
||||
- Extensibility
|
||||
---
|
||||
|
||||
## Also known as
|
||||
@@ -15,11 +17,11 @@ tag:
|
||||
* Filter
|
||||
* Criteria
|
||||
|
||||
## Intent
|
||||
## Intent of Specification Design Pattern
|
||||
|
||||
Encapsulate business rules and criteria that an object must satisfy to enable checking these rules in various parts of the application.
|
||||
|
||||
## Explanation
|
||||
## Detailed Explanation of Specification Pattern with Real-World Examples
|
||||
|
||||
Real-world example
|
||||
|
||||
@@ -29,13 +31,13 @@ Real-world example
|
||||
|
||||
In plain words
|
||||
|
||||
> The Specification design pattern allows for the encapsulation and reuse of business rules and criteria in a flexible, combinable manner.
|
||||
> The Specification design pattern in Java enables the efficient encapsulation and reuse of business rules, offering a flexible and dynamic way to combine criteria for robust software development
|
||||
|
||||
Wikipedia says
|
||||
|
||||
> In computer programming, the specification pattern is a particular software design pattern, whereby business rules can be recombined by chaining the business rules together using boolean logic.
|
||||
|
||||
**Programmatic Example**
|
||||
## Programmatic Example of Specification Pattern in Java
|
||||
|
||||
Let's consider a creature pool example. We have a collection of creatures with specific properties. These properties might belong to a predefined, limited set (represented by enums like `Size`, `Movement`, and `Color`) or they might be continuous values (e.g., the mass of a `Creature`). In cases with continuous values, it's better to use a "parameterized specification," where the property value is provided as an argument when the `Creature` is instantiated, allowing for greater flexibility. Additionally, predefined and/or parameterized properties can be combined using boolean logic, offering almost limitless selection possibilities (this is known as a "composite specification," explained further below). The advantages and disadvantages of each approach are detailed in the table at the end of this document.
|
||||
|
||||
@@ -204,19 +206,23 @@ Console output:
|
||||
12:49:24.818 [main] INFO com.iluwatar.specification.app.App -- Troll [size=large, movement=walking, color=dark, mass=4000.0kg]
|
||||
```
|
||||
|
||||
## Applicability
|
||||
Adopting the Specification pattern significantly enhances the flexibility and reusability of business rules within Java applications, contributing to more maintainable code.
|
||||
|
||||
* Use when you need to filter objects based on different criteria.
|
||||
* Use when the filtering criteria can change dynamically.
|
||||
## When to Use the Specification Pattern in Java
|
||||
|
||||
Apply the Java Specification pattern when
|
||||
|
||||
* You need to filter objects based on different criteria.
|
||||
* The filtering criteria can change dynamically.
|
||||
* Ideal for use cases involving complex business rules that must be reused across different parts of an application.
|
||||
|
||||
## Known Uses
|
||||
## Real-World Applications of Specification Pattern in Java
|
||||
|
||||
* Validating user inputs in enterprise applications.
|
||||
* Filtering search results in e-commerce applications.
|
||||
* Business rule validation in domain-driven design (DDD).
|
||||
|
||||
## Consequences
|
||||
## Benefits and Trade-offs of Specification Pattern
|
||||
|
||||
Benefits:
|
||||
|
||||
@@ -229,13 +235,13 @@ Trade-offs:
|
||||
* Can lead to a proliferation of small classes, increasing complexity.
|
||||
* Might introduce performance overhead due to the dynamic checking of specifications.
|
||||
|
||||
## Related Patterns
|
||||
## Related Java Design Patterns
|
||||
|
||||
* [Composite](https://java-design-patterns.com/patterns/composite/): Often used together with Specification to combine multiple specifications.
|
||||
* [Decorator](https://java-design-patterns.com/patterns/decorator/): Can be used to add additional criteria to a specification dynamically.
|
||||
* [Strategy](https://java-design-patterns.com/patterns/strategy/): Both patterns involve encapsulating a family of algorithms. Strategy encapsulates different strategies or algorithms, while Specification encapsulates business rules.
|
||||
|
||||
## Credits
|
||||
## References and Credits
|
||||
|
||||
* [Domain-Driven Design: Tackling Complexity in the Heart of Software](https://amzn.to/3wlDrze)
|
||||
* [Implementing Domain-Driven Design](https://amzn.to/4dmBjrB)
|
||||
|
||||
Reference in New Issue
Block a user