Dotnet E-commerce Backend Development
Budget: $15 – $25 USD
I’m putting together a full-featured e-commerce web application and I need the server side to be rock solid. The stack is .NET MVC with a REST-style API; C# will be the main language, though you’ll see a little JavaScript on the edge for real-time interactions.
The store itself must do more than handle products and checkout. I want the social layer built in from day one, so the API has to expose:
• User profile endpoints (registration, authentication, avatar upload, settings)
• A private one-to-one messaging system with conversation history and unread counters
• A news-feed style timeline where users can follow activity, like updates, and comment
Beyond those social features, the usual e-commerce flows—product catalog, cart, payment integration, order tracking—need to be cleanly structured and documented. Every route should come with clear request / response models and be covered by unit tests. Swagger or similar auto-generated docs are a must so the front-end team can plug in without guesswork.
I’ll spin up the repo with a basic project skeleton; what I expect back is the full set of API controllers, business logic, and Entity Framework Core models wired to a SQL database, plus concise setup notes so the environment can be reproduced locally or in CI. If something isn’t crystal clear, let’s hash it out early—getting the contract right up front saves time later.
The store itself must do more than handle products and checkout. I want the social layer built in from day one, so the API has to expose:
• User profile endpoints (registration, authentication, avatar upload, settings)
• A private one-to-one messaging system with conversation history and unread counters
• A news-feed style timeline where users can follow activity, like updates, and comment
Beyond those social features, the usual e-commerce flows—product catalog, cart, payment integration, order tracking—need to be cleanly structured and documented. Every route should come with clear request / response models and be covered by unit tests. Swagger or similar auto-generated docs are a must so the front-end team can plug in without guesswork.
I’ll spin up the repo with a basic project skeleton; what I expect back is the full set of API controllers, business logic, and Entity Framework Core models wired to a SQL database, plus concise setup notes so the environment can be reproduced locally or in CI. If something isn’t crystal clear, let’s hash it out early—getting the contract right up front saves time later.