Software Architectural Patterns

 

Architectural Patterns

1. Layered pattern
2. Client-server pattern
3. Master-slave pattern
4. Pipe-filter pattern
5. Broker pattern
6. Peer-to-peer pattern
7. Event-bus pattern
8. Model-view-controller pattern
9. Blackboard pattern
10. Interpreter pattern

Hexagonal Architecture

Onion Architecture

Layered Architecture

Domain Driven Design

Domain-Driven Design is about creating shared understanding of the problem space that is reinforced ubiquitously via conversations, code and diagrams.
Things to know in Domain Driven Design 

1. What is Bounded Context ?
   Bounded context defines tangible boundaries of applicability of some sub-domain. It is an area where a certain sub-domain makes sense, while the others don't. It can be a talk, a presentation, a code project with physical boundaries defined by the artifact.
   
   
2. What is Ubiquitous Language ?
   A Bounded Context is an explicit boundary within which a domain model exists. Inside the boundary all terms and phrases of the Ubiquitous Language have specific meaning, and the model reflects the Language with exactness.

Event Driven Design

Reactive Architecture

https://www.lightbend.com/blog/understand-reactive-architecture-design-and-programming-in-less-than-12-minutes

Reference

• https://towardsdatascience.com/10-common-software-architectural-patterns-in-a-nutshell-a0b47a1e9013
• https://medium.com/@edamtoft/onion-vs-clean-vs-hexagonal-architecture-9ad94a27da91
• https://www.codeguru.com/csharp/understanding-onion-architecture/