Projectsmarkethub
Backend API / Marketplace Platform

MarketHub

A professional .NET 8 marketplace backend API with role-based access, marketplace workflows, PostgreSQL persistence, Swagger, Docker, tests, and CI.

.NET 8ASP.NET CoreEF CorePostgreSQLJWTSwaggerDockerGitHub Actions
View GitHubLive API: Coming soonSwagger: Coming soon
MarketHub backend architecture preview for ASP.NET Core, Swagger, PostgreSQL, JWT, Docker, and CI

GitHub

Repository available

Source code and project documentation

Live API

Coming soon

Swagger

Coming soon

CI / build

Unit tests and GitHub Actions CI workflow

Problem

What needed to be solved

The project is now a backend-first marketplace platform, so the main challenge was organizing real API boundaries for roles, products, carts, orders, reviews, authentication, persistence, and documentation.

Solution

How the project approaches it

I structured MarketHub as a layered ASP.NET Core API with EF Core data access, PostgreSQL persistence, JWT-secured role flows for Admin, Vendor, and Customer users, Swagger API documentation, Dockerized development, unit tests, and a GitHub Actions CI workflow.

Key features

What the project includes

Clean layered architecture
Admin, Vendor, and Customer roles
Product, category, cart, order, and review management
PostgreSQL persistence with EF Core
JWT authentication
Swagger API documentation
Dockerized development environment
Unit tests and CI workflow

Architecture / Technical decisions

Implementation choices worth reviewing

Designed a layered ASP.NET Core API around marketplace workflows, EF Core persistence, and PostgreSQL-backed entities.
Modelled role-based authorization for Admin, Vendor, and Customer flows with JWT authentication.
Kept Swagger, Docker, unit tests, and CI in the delivery scope so the backend can be reviewed beyond source code.

Validation / Quality

How I made the work reviewable

Unit tests and CI workflow included in project scope
Swagger/OpenAPI documentation for endpoint review
Dockerized development environment
Clear role, persistence, and marketplace workflow boundaries

What I learned

Technical takeaway

I learned to approach marketplace work from the API contract first: clear layers, explicit roles, predictable persistence, and repeatable verification make the platform easier to test and extend.