← Back to Categories
</>
CATEGORY

Software Architecture

Architecture patterns and principles for maintainable applications.

GLOSSARY

Terms in Software Architecture

20 terms
01

API Gateway

An API gateway provides a common entry point for clients accessing multiple backend services.

02

CQRS

Command Query Responsibility Segregation separates operations that change state from operations that read state.

03

Circuit Breaker

The circuit breaker pattern temporarily stops calls to an unhealthy dependency to prevent cascading failures.

04

Clean Architecture

Clean Architecture separates business rules from external frameworks and infrastructure.

05

Dependency Inversion Principle

The Dependency Inversion Principle encourages high-level logic to depend on abstractions rather than concrete implementations.

06

Domain-Driven Design

Domain-Driven Design structures software around domain concepts and business rules.

07

Event-Driven Architecture

Event-driven architecture uses events to communicate that something has happened in a system.

08

Facade Pattern

The Facade pattern provides a simplified interface over a more complex subsystem.

09

Factory Pattern

The Factory pattern centralizes object creation so callers do not need to know construction details.

10

Hexagonal Architecture

Hexagonal architecture separates core application logic from external systems through ports and adapters.

11

Layered Architecture

Layered architecture organizes software into logical layers with distinct responsibilities.

12

MVC

Model-View-Controller separates application data, presentation, and request handling responsibilities.

13

Microservices

Microservices architecture divides an application into independently deployable services.

14

Modular Monolith

A modular monolith is a single deployable application organized into well-defined internal modules.

15

Monolithic Architecture

A monolithic application is deployed as a single application unit.

16

Observer Pattern

The Observer pattern allows objects to receive notifications when another object changes state.

17

Open-Closed Principle

The Open-Closed Principle encourages software components to be open for extension but closed for unnecessary modification.

18

SOLID

SOLID is a group of object-oriented design principles intended to support maintainable software.

19

Single Responsibility Principle

A component should have a focused responsibility and a reason to change.

20

Strategy Pattern

The Strategy pattern allows interchangeable algorithms behind a common interface.