Problem and context
The project covered a car-sharing application: reservations, fleet operations and a coherent backend for multiple UI clients. I worked as one of the backend developers delivering the .NET server layer — product brand and end client remain anonymized.
What the solution does
- implements domain logic on a .NET backend,
- applies CQRS to separate write and read paths,
- stores data in PostgreSQL,
- exposes APIs consumed by the frontend and operational processes,
- supports collaboration across PM, client and UI layers.
Architecture
flowchart LR
UI[Frontend / API clients] --> API[.NET backend]
API --> CMD[Commands]
API --> QRY[Queries]
CMD --> DB[(PostgreSQL)]
QRY --> DB
Why it belongs in the portfolio
- shows team delivery on a mobility product,
- evidence of applying CQRS in real .NET work,
- complements the software narrative alongside administration and integration tracks.