01 / Goal
Build the backend workflow, not just isolated endpoints.
The project focused on the server side of an assignment submission platform. The goal was to connect HTTP requests, application logic, file uploads, database storage, and testing into one working backend workflow.
02 / Architecture
A simple request path with clear responsibilities.
Multipart requests added another challenge. Uploaded files had to be received and validated as part of the API workflow instead of treating every request as simple JSON.
03 / What I built
The pieces needed for a real backend workflow.
- REST API endpoints using Actix Web.
- PostgreSQL storage accessed through SQLx.
- Database migrations for repeatable schema changes.
- Multipart file upload handling.
- Workflow testing through Postman.
The project gave me practical experience connecting web service code to persistent data instead of treating database and API work as separate exercises.
04 / Testing
Validate the workflow from the outside.
Postman was used to exercise API flows and multipart upload behavior. That made it possible to test the system as a consumer of the API would see it: request in, response out, and persisted state behind it.
05 / What it demonstrates
Backend fundamentals across the full system.
Requests need clear validation and predictable responses before business logic is useful.
Schema design and migrations shape how safely the application can evolve.
Uploads add state and error cases beyond ordinary JSON payloads.
Testing complete request flows catches integration problems that unit tests can miss.