Problem and context
The client needed a backend for a platform selling licenses to video content: orders, payments, access entitlements and a coherent API contract for the frontend. The work was delivered in a commercial setting with real external integrations — product and client names remain anonymized.
What the solution does
- exposes REST APIs for sales and license-management flows,
- owns server-side order and status business logic,
- integrates payments (Stripe) and video content services (Vimeo),
- persists data in PostgreSQL with focus on process consistency,
- collaborates with the frontend through explicit API contracts.
Architecture
flowchart LR
FE[Frontend] --> API[.NET REST backend]
API --> DB[(PostgreSQL)]
API --> STR[Stripe]
API --> VIM[Vimeo]
Why it belongs in the portfolio
- shows end-to-end backend ownership, not only a supporting role in a larger team,
- combines software delivery with payment and content integrations,
- evidence of .NET + PostgreSQL competence in a commercial product.