>ŁADOWANIE // PROJECT DETAILS

PARSING ARCHITECTURE, DIAGRAMS & API ENDPOINTS

>ŁADOWANIE // ŁADOWANIE

INICJALIZACJA WIDOKU

Powrót do projektów

Zobacz na GitHubie

Ukończononestjspostgrestypescriptjesteslintdockergithubactionspostmanswagger

Backend Mikroserwisowy

Architektura mikroserwisów z NestJS, PostgreSQL i Dockerem zintegrowana przez centralną bramę API Gateway.

Problem i rozwiązanie

Rozdzielenie routingu (API Gateway), logiki domenowej (niezależne serwisy) i bazy danych w celu autonomicznego wdrażania i skalowania.

Funkcje

Rozdzielone mikroserwisy dla Produktów i Zamówień
API Gateway do centralnego routingu i zabezpieczeń
Baza danych PostgreSQL koordynowana przez Docker Compose
Struktura monorepo zarządzana za pomocą TurboRepo
Automatyczne wdrożenia Docker Hub za pośrednictwem GitHub Actions CI/CD
Kompleksowe testy jednostkowe w Jest

Stos technologiczny

Technologia	Wersja	Cel	Dlaczego wybrano
TypeScript	^5.7.3	Primary language for all services	Type safety, NestJS ecosystem standard
NestJS	^11.0.1	Application framework	Modular architecture, dependency injection, TypeScript-first
TypeORM	^0.3.27	ORM for PostgreSQL access	Active Record/Repository pattern, NestJS integration
PostgreSQL	15	Primary database	JSONB support, ACID compliance, reliability
Docker	—	Containerization for all services	Consistent environments, reproducible deployments
Turborepo	^2.5.8	Monorepo task orchestration	Fast parallel builds, caching, npm workspaces integration
GitHub Actions	—	CI/CD pipeline execution	Free for public repos, tight Git integration
Jest	^30.0.0	Unit testing framework	NestJS default, snapshot support
Swagger	^11.2.0	API documentation	Auto-generates OpenAPI from decorators

Architektura

Client

API Gateway

:3000

Products Service

:3001

Orders Service

:3002

PostgreSQL

:5432

Core System Components

API Gateway for routing requests to internal services
Products & Orders service as independent NestJS services
Docker Compose orchestration
PostgreSQL container

Infrastructure

GitHub Actions CI (lint, test, build)
Docker Hub CD image deployment
Environment variable management

Struktura projektu

.github

workflows

apps

api-gateway

orders-service

products-service

libs

common

docker-compose.ymlOrchestrates all services and PostgreSQL database

Punkty końcowe API

API Gateway (port 3000)

Metoda	Trasa	Cel
GET	/products	List all products
GET	/products/:id	Get product by ID
POST	/products	Create product
PATCH	/products/:id	Update product
DELETE	/products/:id	Delete product
GET	/orders	List all orders
GET	/orders/:id	Get order by ID
POST	/orders	Create order

Products Service (port 3001)

Metoda	Trasa	Cel
POST	/products	Create product
GET	/products	List all products
GET	/products/:id	Get product by ID
PATCH	/products/:id	Update product
DELETE	/products/:id	Delete product

Orders Service (port 3002)

Metoda	Trasa	Cel
POST	/orders	Create order
GET	/orders	List all orders
GET	/orders/:id	Get order by ID

Projekt bazy danych

product

6 cols

idPK

SERIAL

code

VARCHAR

name

VARCHAR

description

VARCHAR

price

DECIMAL

image

VARCHAR

order

4 cols

idPK

SERIAL

customer

JSONB

products

JSONB

totalAmount

DECIMAL

product

Kolumna	Typ	Uwagi
idPK	SERIAL	Auto-generated primary key
code	VARCHAR	Product SKU/code
name	VARCHAR	Product display name
description	VARCHAR	Product description
price	DECIMAL	Product price
image	VARCHAR	Image URL

No explicit indexes beyond primary key. No unique constraints on code.

order

Kolumna	Typ	Uwagi
idPK	SERIAL	Auto-generated primary key
customer	JSONB	Stores {name, phone}
products	JSONB	Array of {id, name, rate, qty}
totalAmount	DECIMAL	Total order amount

Products stored as JSONB snapshot — intentional denormalization. No foreign keys to product table.

No foreign key relationships. Order.products is a JSONB snapshot — orders are self-contained records that do not reference the product table. Product price changes do not affect existing orders.

Kluczowe decyzje projektowe

Shared PostgreSQL Database

Decyzja: Both services connect to the same PostgreSQL instance and database (procura_db)

Dlaczego: Simplifies development and deployment — one database to manage

Korzyści: Simpler infrastructure, lower resource usage, easier local development

Kompromisy: Violates database-per-service principle, creates hidden coupling, makes independent scaling harder

JSONB for Order Products

Decyzja: Order entity stores product data as JSONB rather than foreign key references

Dlaczego: Decouples order data from product lifecycle — orders are immutable snapshots

Korzyści: Orders are self-contained, product changes don't affect historical orders

Kompromisy: No referential integrity, data duplication, no automatic product validation on order creation

API Key Authentication

Decyzja: Simple static API key in x-api-key header, compared against environment variable

Dlaczego: Simplest possible authentication for demonstration purposes

Korzyści: Minimal implementation, no token management, no state

Kompromisy: No user identity, no fine-grained permissions, key is static and shared

HTTP-based Inter-service Communication

Decyzja: API Gateway communicates with downstream services via synchronous HTTP (Axios)

Dlaczego: Simplest approach for synchronous request-response pattern

Korzyści: Easy to understand, debug, and test; standard HTTP tooling

Kompromisy: Synchronous coupling, no retry/circuit breaker, no async processing

Multi-stage Docker Builds

Decyzja: Each service uses a 3-stage Dockerfile (deps → builder → runner)

Dlaczego: Minimizes final image size and attack surface

Korzyści: Production images contain only runtime dependencies and compiled code

Kompromisy: Build time for each stage, no layer caching optimization for src changes

TypeORM synchronize: true

Decyzja: Both services use synchronize: true in TypeORM config

Dlaczego: Auto-creates/updates database schema from entities during development

Korzyści: No migration files needed, schema stays in sync with code

Kompromisy: Dangerous in production — can cause data loss on schema changes

Testy

Jest ^30.0.0 with ts-jest ^29.2.5•34 testów jednostkowych

Co jest testowane

API Gateway: root health check, all proxy operations (products + orders)
Products Service: controller methods (create, findAll, findOne, update, remove)
Products Service: service methods (create, findAll, findOne, update, remove)
Orders Service: controller methods (create, findAll, findOne, id conversion)
Orders Service: service methods (create, findAll, findOne)

Brakujące pokrycie

Integration tests with real database
API Gateway ↔ Service integration tests
Middleware tests for API key validation
Validation error scenario tests
Error path tests (404, 500 scenarios)

Kluczowe wyzwania

Coordinating multiple services while ensuring fault isolation
Setting up CI/CD pipelines for multi-image Docker builds
Managing environment variables cleanly inside Docker

Kluczowe wnioski

Effective use of API Gateway pattern
Advanced Docker container orchestration with dependencies
Dependency isolation using monorepo tooling (TurboRepo)

>ŁADOWANIE // PROJECT DETAILS

PARSING ARCHITECTURE, DIAGRAMS & API ENDPOINTS

Powrót do projektów

Zobacz na GitHubie

Ukończononestjspostgrestypescriptjesteslintdockergithubactionspostmanswagger

Backend Mikroserwisowy

Architektura mikroserwisów z NestJS, PostgreSQL i Dockerem zintegrowana przez centralną bramę API Gateway.

Problem i rozwiązanie

Rozdzielenie routingu (API Gateway), logiki domenowej (niezależne serwisy) i bazy danych w celu autonomicznego wdrażania i skalowania.

Funkcje

Rozdzielone mikroserwisy dla Produktów i Zamówień
API Gateway do centralnego routingu i zabezpieczeń
Baza danych PostgreSQL koordynowana przez Docker Compose
Struktura monorepo zarządzana za pomocą TurboRepo
Automatyczne wdrożenia Docker Hub za pośrednictwem GitHub Actions CI/CD
Kompleksowe testy jednostkowe w Jest

Stos technologiczny

Technologia	Wersja	Cel	Dlaczego wybrano
TypeScript	^5.7.3	Primary language for all services	Type safety, NestJS ecosystem standard
NestJS	^11.0.1	Application framework	Modular architecture, dependency injection, TypeScript-first
TypeORM	^0.3.27	ORM for PostgreSQL access	Active Record/Repository pattern, NestJS integration
PostgreSQL	15	Primary database	JSONB support, ACID compliance, reliability
Docker	—	Containerization for all services	Consistent environments, reproducible deployments
Turborepo	^2.5.8	Monorepo task orchestration	Fast parallel builds, caching, npm workspaces integration
GitHub Actions	—	CI/CD pipeline execution	Free for public repos, tight Git integration
Jest	^30.0.0	Unit testing framework	NestJS default, snapshot support
Swagger	^11.2.0	API documentation	Auto-generates OpenAPI from decorators

Architektura

Client

API Gateway

:3000

Products Service

:3001

Orders Service

:3002

PostgreSQL

:5432

Core System Components

API Gateway for routing requests to internal services
Products & Orders service as independent NestJS services
Docker Compose orchestration
PostgreSQL container

Infrastructure

GitHub Actions CI (lint, test, build)
Docker Hub CD image deployment
Environment variable management

Struktura projektu

.github

workflows

apps

api-gateway

orders-service

products-service

libs

common

docker-compose.ymlOrchestrates all services and PostgreSQL database

Punkty końcowe API

API Gateway (port 3000)

Metoda	Trasa	Cel
GET	/products	List all products
GET	/products/:id	Get product by ID
POST	/products	Create product
PATCH	/products/:id	Update product
DELETE	/products/:id	Delete product
GET	/orders	List all orders
GET	/orders/:id	Get order by ID
POST	/orders	Create order

Products Service (port 3001)

Metoda	Trasa	Cel
POST	/products	Create product
GET	/products	List all products
GET	/products/:id	Get product by ID
PATCH	/products/:id	Update product
DELETE	/products/:id	Delete product

Orders Service (port 3002)

Metoda	Trasa	Cel
POST	/orders	Create order
GET	/orders	List all orders
GET	/orders/:id	Get order by ID

Projekt bazy danych

product

6 cols

idPK

SERIAL

code

VARCHAR

name

VARCHAR

description

VARCHAR

price

DECIMAL

image

VARCHAR

order

4 cols

idPK

SERIAL

customer

JSONB

products

JSONB

totalAmount

DECIMAL

product

Kolumna	Typ	Uwagi
idPK	SERIAL	Auto-generated primary key
code	VARCHAR	Product SKU/code
name	VARCHAR	Product display name
description	VARCHAR	Product description
price	DECIMAL	Product price
image	VARCHAR	Image URL

No explicit indexes beyond primary key. No unique constraints on code.

order

Kolumna	Typ	Uwagi
idPK	SERIAL	Auto-generated primary key
customer	JSONB	Stores {name, phone}
products	JSONB	Array of {id, name, rate, qty}
totalAmount	DECIMAL	Total order amount

Products stored as JSONB snapshot — intentional denormalization. No foreign keys to product table.

No foreign key relationships. Order.products is a JSONB snapshot — orders are self-contained records that do not reference the product table. Product price changes do not affect existing orders.

Kluczowe decyzje projektowe

Shared PostgreSQL Database

Decyzja: Both services connect to the same PostgreSQL instance and database (procura_db)

Dlaczego: Simplifies development and deployment — one database to manage

Korzyści: Simpler infrastructure, lower resource usage, easier local development

Kompromisy: Violates database-per-service principle, creates hidden coupling, makes independent scaling harder

JSONB for Order Products

Decyzja: Order entity stores product data as JSONB rather than foreign key references

Dlaczego: Decouples order data from product lifecycle — orders are immutable snapshots

Korzyści: Orders are self-contained, product changes don't affect historical orders

Kompromisy: No referential integrity, data duplication, no automatic product validation on order creation

API Key Authentication

Decyzja: Simple static API key in x-api-key header, compared against environment variable

Dlaczego: Simplest possible authentication for demonstration purposes

Korzyści: Minimal implementation, no token management, no state

Kompromisy: No user identity, no fine-grained permissions, key is static and shared

HTTP-based Inter-service Communication

Decyzja: API Gateway communicates with downstream services via synchronous HTTP (Axios)

Dlaczego: Simplest approach for synchronous request-response pattern

Korzyści: Easy to understand, debug, and test; standard HTTP tooling

Kompromisy: Synchronous coupling, no retry/circuit breaker, no async processing

Multi-stage Docker Builds

Decyzja: Each service uses a 3-stage Dockerfile (deps → builder → runner)

Dlaczego: Minimizes final image size and attack surface

Korzyści: Production images contain only runtime dependencies and compiled code

Kompromisy: Build time for each stage, no layer caching optimization for src changes

TypeORM synchronize: true

Decyzja: Both services use synchronize: true in TypeORM config

Dlaczego: Auto-creates/updates database schema from entities during development

Korzyści: No migration files needed, schema stays in sync with code

Kompromisy: Dangerous in production — can cause data loss on schema changes

Testy

Jest ^30.0.0 with ts-jest ^29.2.5•34 testów jednostkowych

Co jest testowane

API Gateway: root health check, all proxy operations (products + orders)
Products Service: controller methods (create, findAll, findOne, update, remove)
Products Service: service methods (create, findAll, findOne, update, remove)
Orders Service: controller methods (create, findAll, findOne, id conversion)
Orders Service: service methods (create, findAll, findOne)

Brakujące pokrycie

Integration tests with real database
API Gateway ↔ Service integration tests
Middleware tests for API key validation
Validation error scenario tests
Error path tests (404, 500 scenarios)

Kluczowe wyzwania

Coordinating multiple services while ensuring fault isolation
Setting up CI/CD pipelines for multi-image Docker builds
Managing environment variables cleanly inside Docker

Kluczowe wnioski

Effective use of API Gateway pattern
Advanced Docker container orchestration with dependencies
Dependency isolation using monorepo tooling (TurboRepo)