← Back to Categories
</>
CATEGORY

Backend Architecture

Core concepts used to design and structure backend applications.

GLOSSARY

Terms in Backend Architecture

21 terms
01

Application Boundary

An application boundary separates one responsibility or subsystem from another.

02

Backend

The backend is the server-side part of an application responsible for business logic, data access, and APIs.

03

Backend Contract

A backend contract defines the expected interaction between an API and its consumers.

04

Business Logic

Business logic represents the rules and operations specific to an application's domain.

05

Configuration Layer

A configuration layer centralizes environment-specific application settings.

06

Controller

A controller coordinates incoming requests with application logic and responses.

07

DTO

A Data Transfer Object carries structured data between application boundaries.

08

Data Access Layer

The data access layer handles communication between application logic and persistent storage.

09

Dependency Injection

Dependency injection supplies required dependencies to components rather than making them construct those dependencies themselves.

10

Deserialization

Deserialization converts serialized data into an application representation.

11

Domain Model

A domain model represents important concepts and rules of a particular business domain.

12

Feature Module

A feature module groups related backend functionality around a business capability.

13

Inversion of Control

Inversion of control transfers responsibility for creating or coordinating dependencies to an external mechanism.

14

Middleware Chain

A middleware chain is a sequence of processing components through which requests and responses pass.

15

Repository Pattern

The repository pattern separates data-access operations from business logic.

16

Request Lifecycle

The request lifecycle describes the stages an HTTP request passes through before a response is returned.

17

Route

A route maps an incoming URL and HTTP method to application logic.

18

Schema

A schema defines the expected structure and validation rules of application data.

19

Separation of Concerns

Separation of concerns keeps different responsibilities in distinct parts of an application.

20

Serialization

Serialization converts application objects or data structures into a transferable representation.

21

Service Layer

A service layer contains reusable business logic separately from request-handling code.