Sairyss/domain-driven-hexagon

Architecture

This is an attempt to combine multiple architectural patterns and styles together, such as:

Before we begin, here are the PROS and CONS of using a complete architecture like this:

• Domain-Driven Design (DDD)
• Hexagonal (Ports and Adapters) Architecture)
• Secure by Design
• Clean Architecture
• Onion Architecture
• SOLID Principles
• Software Design Patterns
• Independent of external frameworks, technologies, databases, etc. Frameworks and external resources can be plugged/unplugged with much less effort.
• Easily testable and scalable.
• More secure. Some security principles are baked in design itself.
• The solution can be worked on and maintained by different teams, without stepping on each other's toes.
• Easier to add new features. As the system grows over time, the difficulty in adding new features remains constant and relatively small.
• If the solution is properly broken apart along bounded context lines, it becomes easy to convert pieces of it into microservices if needed.
• This is a sophisticated architecture which requires a firm understanding of quality software principles, such as SOLID, Clean/Hexagonal Architecture, Domain-Driven Design, etc. Any team implementing s