Software Architecture and Software Design
Tags: software, architecture, design, patterns
Published: 2022-07-27 16:03:35

Based on both key definitions, software architecture and software design, we can lay down an organization of software principles, methodologies and patterns currently applied in modern software development and technology innovations.

## Software Architecture

It's a high level blueprint for a system.
It defines the structural elements like subsystems, roles, relationships and responsibilities meaning it lays down the architecture style, patterns that will guide the software design.
Software architecture directly deals with arranging this elements like servers, databases, APIs, clients or users of the software application, etc in order to fulfill business requirements.

## Software Design

Implies decisions at a lower level of detail as it provides an implementation plans for the laid out architecture.
Software designers will decide on the specifications, contracts used in these subsystems that later software engineers will implement.

---

# Organization of software principles, methodologies and patterns 

Index of software concepts:

1. [Software architecture style](#001)
2. [Software architecture patterns](#002)
3. [Software design methodologies](#003)
4. [Software design patterns](#004)
5. [Programming paradigms](#005)
6. [Clean code principles](#006)

## 1. Software Architecture Style <a name="001"></a>

**Based on Structure (separation of concerns)**

- Layered architecture (N-tier)
- Hexagonal architecture (Ports & Adapters)

**Based on distribution of the application**

- Monolith architecture
- Microservices architecture
   - Microservices patterns

**Events based**

- Event Driven architecture

**Cloud based**

- Serverless architecture

**Network based**

- REST over HTTP

<!--
Expand on [software architecture styles](url)
-->

## 2. Software Architecture Patterns <a name="002"></a>

**Based on data management**

- Database per Service
- Shared database
- CQRS
- Domain event
- Event sourcing

**Based on transactional messaging**

- Transactional outbox

**Based on security**

- Access tokens
- Oauth
- Session

**Based on observability**

- Log aggregation
- Application metrics
- Exception tracking
- Health check API

<!-- 
Expand on [software architecture patterns](https://dev.to/franckweb/software-architecture-patterns-for-common-problems-1k18)
-->

## 3. Software Design Methodologies <a name="003"></a>

- Domain Driven Design (DDD)
- Behavior Driven Development (BDD)
- Test Driven Development (TDD)

<!-- 
Expand on [software design methodologies](url)
-->

## 4. Software Design Patterns <a name="004"></a>

- Creational Patterns
- Structural Patterns
- Behavioral Patterns 

Expand on [software design patterns](https://dev.to/franckweb/software-architecture-design-patterns-516j)

## 5. Programming Paradigms <a name="005"></a>

- Object Oriented Programming (OOP)
  - Composition over inheritance
  - SOLID
     - Single-responsiblity Principle
     - Open-closed Principle
     - Liskov Substitution Principle
     - Interface Segregation Principle
     - Dependency Inversion Principle
- Functional Programming

<!-- 
Expand on [programming paradigms](url)
-->

## 6. Basic principles <a name="006"></a>

- Clean Code
- DRY: Don't repeat yourself
- KISS: Keep it stupid simple
- YAGNI: You aren't going to need it

<!-- 
Expand on [basic software principles](url).
-->

Take into account that all these architectural principles, methodologies and patterns are no substitute for making your own decisions. You need to balance them according to business requirements of your software application.