https://github.com/hexagonframework/hexagonal-architecture-demo

https://github.com/hexagonframework/hexagonal-architecture-demo

cors ddd hexagonal-architecture

Last synced: 8 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/hexagonframework/hexagonal-architecture-demo
• Owner: hexagonframework
• License: apache-2.0
• Created: 2018-05-08T02:34:23.000Z (about 8 years ago)
• Default Branch: master
• Last Pushed: 2018-05-10T07:35:21.000Z (about 8 years ago)
• Last Synced: 2025-08-08T09:04:48.389Z (10 months ago)
• Topics: cors, ddd, hexagonal-architecture
• Language: Java
• Size: 491 KB
• Stars: 14
• Watchers: 2
• Forks: 3
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# hexagonal-architecture-demo

> 基于DDD和六边形架构的微服务DEMO

## Command Query CRUD Responsibility Segregation

Not every piece of software is equally important...

Not every piece will decide about company / product success or can cause not reversible

negative business consequences like materialise brand risk or money loses.

On the other hand scalability or non functional requirements are different for different activities in software.

To accommodate to those differences, separate architectural patterns are applied:

![Command Query CRUD Responsibility Segregation](command-query-crud.png)

## Hexagonal Architecture

Only the most valuable part of that enterprise software is embedded in hexagonal architecture -

complex business processing modeled in form of the Domain Model.

![Domain Model embedded in hexagonal architecture](hexagon.png)

**Application Services** - providing entry point to Domain Model functionality,

Application Services are ports for Primary / Driving Adapters like RESTfull endpoints.

**Domain Model** - Object Oriented (in that case) piece of software modeling business rules, invariants,

calculations and processing variants.

Thanks to hexagon can be as clean and simple as possible - separating essential complexity of pure business

from accidental complexity of technical choices, free of technical and convention constraints.

**Ports** - contract defined by Domain Model expressing expectations from external resources (services, database or other models).

Declared interfaces alongside with IN-OUT parameters are Ports for Secondary / Driven Adapters like repository implementation.

**Adapters** - integration of the technology (REST, database, external services, etc.) with the Domain Model.

Making useful application from the Domain Model and the technology.