Case Study

CongoCart

An e-commerce backend shaped around cart behavior, secure checkout, and order workflows that stay dependable as traffic and product requirements grow.

Back to Portfolio GitHub

.NET 8 ASP.NET Core JWT Authentication PostgreSQL Clean Architecture

Problem Space

What needed to work well

E-commerce backends carry a lot of pressure: carts must stay consistent, checkout must feel secure, and order behavior has to remain trustworthy even as concurrency rises.

The main challenge was designing APIs that could support this without tightly coupling business logic to infrastructure or letting edge cases create brittle user journeys.

Responsibilities

What I owned

Designed RESTful APIs for carts, checkout, and order management.
Implemented JWT-based authentication and role-aware authorization.
Used clean architecture to keep use cases isolated from infrastructure.
Handled validation, error consistency, and backend workflow clarity.

Architecture

How the system was organized

I used clean architecture so the platform could support ongoing feature growth without blending domain logic, API handling, and persistence concerns into the same layer.

API layer for routing, contracts, and validation
Application layer for checkout and order workflows
Domain layer for business rules and entity logic
Infrastructure layer for persistence and authentication support

Security

Protecting the checkout path

In commerce systems, trust breaks quickly if sensitive operations are weakly protected, so the backend needed a strong security baseline from the first iteration.

JWT authentication for stateless API access
Authorization checks for cart and order-sensitive operations
Input validation to reduce malformed and risky requests
Centralized exception handling for safe API responses

Reliability

Preparing for scale and consistency

The backend was designed to stay predictable under concurrent user activity by keeping workflows clear and reducing unnecessary coupling between reads, writes, and surrounding infrastructure.

Optimized database access for cart and order behavior
Stateless service design for easier horizontal scaling
Clear separation between command-heavy and read-heavy concerns

Next Iteration

What I would add next

Redis caching for cart and product-adjacent data.
Background workers for post-checkout processing.
Structured monitoring and logging for production support.
Rate limiting and throttling on public-facing endpoints.

Next Move

Building commerce workflows that need to feel dependable?

That kind of work fits me well, especially when the backend needs equal attention on security, predictability, and future-friendly structure.

Email Me Portfolio Contact