Peer-to-Peer
Anemic Models
PoSA Patterns
Keep framework code distant
Component Principles
Domain Language
Minimize cyclomatic complexity
Transaction Script
Enterprise Patterns
Encapsulate what varies
SOA
Use meaningful names
Software Design & Architecture
Functional Programming
Command Query Separation
Object Oriented Programming
Message Queues / Streams
Model-View Controller
Tests should be fast and independent
Abstract Classes
Microservices
Abstraction
Pure functions
Inheritance
Domain Models
Event Sourcing
Publish-Subscribe
Paradigm Features
DTOs
Meaningful names over Comments
Layered
GoF Design Patterns
Use correct constructs
Client-Server
CQRS
Design Patterns
Layered Architectures
Messaging
Primary Principles
Coupling and Cohesion
Indentation and Code Style
Organize code by the actor it belongs to
Blackboard Pattern
Architectural Patterns
Interfaces
Mappers
Identity Maps
SOLID
Scope / Visibility
Architectural Principles
Monolithic
Component-Based
Polymorphism
Structural
Programming Paradigms
Design Principles
Architectural Styles
font color=\"0\
Value Objects
Clean Code Principles
Composition over Inheritance
Clean Code
Boundaries
Minimap of Topics
Repositories
Domain-Driven Design
Program against abstractions
Be Consistent
Event-Driven
Keep it simple and refactor often
Policy vs Detail
Keep Learning
Model-Driven Design
Structured Programming
Concrete Classes
Class Invariants
Encapsulation
Distributed
Commands / Queries
Entities
ORMs
YAGNI
Serverless Architecture
Hollywood principle
Microkernel
DRY
Use Cases
