.NET Core API & SQL Server
Budget: $8 – $15 AUD
An Angular SPA and several deployment scripts in PowerShell are already working; the missing piece is a solid .NET Core backend that will expose RESTful endpoints, handle data in SQL Server, and secure everything with modern authentication and authorization.
Scope of work
• Build an ASP.NET Core API (latest LTS) that follows clean-architecture principles.
• Design the SQL Server schema and provide Entity Framework Core migrations so the database can be recreated from source control at any time.
• Implement token-based authentication (JWT) and role-based authorization ready to plug into the existing Angular front-end.
• Cover the code with unit tests and document every endpoint through Swagger/OpenAPI so the front-end team can start consuming it immediately.
Acceptance criteria
1. All endpoints return the expected payloads and HTTP status codes.
2. `dotnet test` passes with no failures, `dotnet ef database update` creates the schema from scratch, and `dotnet run` starts the service without manual steps.
3. A Postman or Swagger collection demonstrates successful login, protected calls, and typical CRUD operations.
4. Source code is delivered via Git with clear commit history and a short README explaining environment variables, build commands, and deployment steps.
This backend will be the backbone of the application, so code readability, SOLID practices, and helpful comments are highly valued. If you have questions about the existing Angular components or the PowerShell deployment flow, let me know—everything is ready to be integrated.
Scope of work
• Build an ASP.NET Core API (latest LTS) that follows clean-architecture principles.
• Design the SQL Server schema and provide Entity Framework Core migrations so the database can be recreated from source control at any time.
• Implement token-based authentication (JWT) and role-based authorization ready to plug into the existing Angular front-end.
• Cover the code with unit tests and document every endpoint through Swagger/OpenAPI so the front-end team can start consuming it immediately.
Acceptance criteria
1. All endpoints return the expected payloads and HTTP status codes.
2. `dotnet test` passes with no failures, `dotnet ef database update` creates the schema from scratch, and `dotnet run` starts the service without manual steps.
3. A Postman or Swagger collection demonstrates successful login, protected calls, and typical CRUD operations.
4. Source code is delivered via Git with clear commit history and a short README explaining environment variables, build commands, and deployment steps.
This backend will be the backbone of the application, so code readability, SOLID practices, and helpful comments are highly valued. If you have questions about the existing Angular components or the PowerShell deployment flow, let me know—everything is ready to be integrated.