mirror of
https://github.com/tiennm99/java-design-patterns.git
synced 2026-08-19 22:23:55 +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:
+22
-20
@@ -1,16 +1,18 @@
|
||||
---
|
||||
title: Domain Model
|
||||
title: "Domain Model Pattern in Java: Building Robust Business Logic"
|
||||
shortTitle: Domain Model
|
||||
description: "Learn about the Domain Model pattern in Java design with detailed explanations, examples, and applications. Improve your software's modularity, maintainability, and scalability."
|
||||
category: Structural
|
||||
language: en
|
||||
tag:
|
||||
- Abstraction
|
||||
- Business
|
||||
- Data processing
|
||||
- Domain
|
||||
- Encapsulation
|
||||
- Layered architecture
|
||||
- Persistence
|
||||
- Polymorphism
|
||||
- Abstraction
|
||||
- Business
|
||||
- Data processing
|
||||
- Domain
|
||||
- Encapsulation
|
||||
- Layered architecture
|
||||
- Persistence
|
||||
- Polymorphism
|
||||
---
|
||||
|
||||
## Also known as
|
||||
@@ -18,11 +20,11 @@ tag:
|
||||
* Conceptual Model
|
||||
* Domain Object Model
|
||||
|
||||
## Intent
|
||||
## Intent of Domain Model Design Pattern
|
||||
|
||||
The Domain Model pattern aims to create a conceptual model in your software that matches the real-world system it's designed to represent. It involves using rich domain objects that encapsulate both data and behavior relevant to the application domain.
|
||||
The Domain Model pattern aims to create a conceptual model in your software that matches the real-world system it's designed to represent. It involves using rich domain objects that encapsulate both data and behavior relevant to the application domain, ensuring business logic is centralized.
|
||||
|
||||
## Explanation
|
||||
## Detailed Explanation of Domain Model Pattern with Real-World Examples
|
||||
|
||||
Real-world example
|
||||
|
||||
@@ -32,7 +34,7 @@ In plain words
|
||||
|
||||
> The Domain Model is an object model of the domain that incorporates both behavior and data.
|
||||
|
||||
**Programmatic Example**
|
||||
## Programmatic Example of Domain Model Pattern in Java
|
||||
|
||||
Let's assume that we need to build an e-commerce web application. While analyzing requirements you will notice that there are few nouns you talk about repeatedly. It’s your Customer, and a Product the customer looks for. These two are your domain-specific classes and each of that classes will include some business logic specific to its domain.
|
||||
|
||||
@@ -223,28 +225,28 @@ The program output:
|
||||
12:17:23.846 [main] INFO com.iluwatar.domainmodel.Customer -- Tom bought: Eggs - $10.00, Cheese - $20.00
|
||||
```
|
||||
|
||||
## Class diagram
|
||||
## Detailed Explanation of Domain Model Pattern with Real-World Examples
|
||||
|
||||

|
||||
|
||||
## Applicability
|
||||
## When to Use the Domain Model Pattern in Java
|
||||
|
||||
* Appropriate in complex applications with rich business logic.
|
||||
* When the business logic or domain complexity is high and requires a model that closely represents real-world entities and their relationships.
|
||||
* Suitable for applications where domain experts are involved in the development process to ensure the model accurately reflects domain concepts.
|
||||
|
||||
## Tutorials
|
||||
## Domain Model Pattern Java Tutorials
|
||||
|
||||
* [Architecture patterns: domain model and friends (Inviqa)](https://inviqa.com/blog/architecture-patterns-domain-model-and-friends)
|
||||
|
||||
## Known Uses
|
||||
## Real-World Applications of Domain Model Pattern in Java
|
||||
|
||||
* Enterprise applications (ERP, CRM systems)
|
||||
* Financial systems (banking, trading platforms)
|
||||
* Healthcare applications (patient records management)
|
||||
* E-commerce platforms (product catalogs, shopping carts)
|
||||
|
||||
## Consequences
|
||||
## Benefits and Trade-offs of Domain Model Pattern
|
||||
|
||||
Benefits:
|
||||
|
||||
@@ -259,14 +261,14 @@ Trade-offs:
|
||||
* Performance Concerns: Rich domain objects with complex behaviors might lead to performance bottlenecks, requiring careful optimization.
|
||||
* Learning Curve: Requires a good understanding of the domain and may involve a steep learning curve for developers unfamiliar with the domain concepts.
|
||||
|
||||
## Related Patterns
|
||||
## Related Java Design Patterns
|
||||
|
||||
* [Data Access Object (DAO)](https://java-design-patterns.com/patterns/dao/): For abstracting and encapsulating all access to the data source.
|
||||
* [Repository](https://java-design-patterns.com/patterns/repository/): Mediates between the domain and data mapping layers, acting like an in-memory domain object collection.
|
||||
* [Service Layer](https://java-design-patterns.com/patterns/service-layer/): Defines an application's boundary with a layer of services that establishes a set of available operations and coordinates the application's response in each operation.
|
||||
* [Unit of Work](https://java-design-patterns.com/patterns/unit-of-work/): Maintains a list of objects affected by a business transaction and coordinates the writing out of changes.
|
||||
|
||||
## Credits
|
||||
## References and Credits
|
||||
|
||||
* [Domain-Driven Design: Tackling Complexity in the Heart of Software](https://amzn.to/3vMCjnP)
|
||||
* [Implementing Domain-Driven Design](https://amzn.to/4cUX4OL)
|
||||
|
||||
Reference in New Issue
Block a user