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
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

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.

Related work

More case studies

Back to Projects
SmartSim Analytics simulation analytics preview showing CSV/JSON input, Python analysis, dashboard output, and reporting
Simulation Analytics / Full-Stack Data Platform
SA

SmartSim Analytics

A full-stack simulation analytics platform for CSV/JSON exports, deterministic Python analysis, KPIs, anomaly detection, trend and stability checks, and PDF reporting.

ReactTypeScriptNode.jsExpress+6
Live DemoComing soon
API DemoComing soon
GitHub
Smart Match recruitment platform screenshot showing candidate and recruiter dashboard screens
Full-Stack Platforms
SM

Smart Match - Internship & Freelance Matching Platform

A full-stack matching platform for candidates, recruiters, companies, offers, applications, notifications, and AI-assisted matching results.

Spring BootMongoDBAngularReact Native+4
GitHub
Assistant d'Analyse des Competences analytics dashboard screenshot with Excel import and class competency reporting
Education Analytics / Desktop App
AD

Assistant d'Analyse des Compétences

A local-first analytics assistant for teachers to import Excel competency reports, analyze class and student performance, identify strongest and weakest competencies, and generate printable reports with French/Arabic support.

ReactTypeScriptViteElectron+5
Live DemoComing soon
Desktop ReleaseComing soon
GitHub