Full-stack Delivery service project.
Project that work with 2 different sides:
- Frontend: writen with React;
- Backend: writen on Java with Spring Boot framework;
This project was made to test acquired skills in full-stack development. Backend fully writen in Java with Spring Framework. Key backend features:
- JWT system implementation;
- Spring Security authorization;
- Database with several related tables;
Frontend writen with React, for requests and responses i used AXIOS. Page styling made with Tailwindcss. Key frontend features:
- Axios usage for requests/response;
- Multipage React app (Routing and Navigation);
Currently service made for only 2 actors:
- User;
- Admin (Worker);
User have 2 option how he can start using service: login in his existing account or create new one. If user already have account he can login to service by pressing login button on navbar and fill login form, wich in case the credentials was entered correctly - user redirected to his profile. User also can see his dashboard, where his packages gonna display.
Admin, or worker - has more available features than regular user. Admin can manage registered users profiles, can see all packages and edit them. And he also can receive and deliver packages;
Whole system currently handle 3 controllers.
- UserManagement controller
- Package controller
- Department controller (Uses only in development, not implemented in project)
| Method | URL | Params | Description |
|---|---|---|---|
| POST | /auth/registration | @RequestBody UserRR req | Register new user |
| POST | /auth/login | @RequestBody UserRR req | Login user |
| POST | /auth/refresh | @RequestBody UserRR req | Refresh user's token |
| GET | /admin/get-all-users | - | Return all users |
| GET | /admin/get-user/{userId} | @PathVariable int userId | Return user by its ID |
| PUT | /admin/update/{userID} | @PathVariable int userId, @RequestBody UserRR req | Update user |
| DELETE | /admin/delete/{userID} | @PathVariable int userId | Delete user by its ID |
| GET | /cred/get-profile | - | Return user profile based on token |
| Method | URL | Params | Description |
|---|---|---|---|
| GET | /get-all | - | Return all packages |
| GET | /get/{id} | @PathVariable long id | Return package by its ID |
| PUT | /edit/{packageID} | @PathVariable long packageId, @RequestBody PackageRR req | Edit package by its ID |
| PUT | /status/{packageId} | @PathVariable long packageId, @RequestBody PackageRR req | Set new status for package |
| POST | /new | @RequestBody PackageRR request | Create new package |
| GET | /get/my | - | Return users packages base on its token |
| Method | URL | Params | Description |
|---|---|---|---|
| GET | /get-all | - | Return all departments |
| GET | /{id} | @PathVariable String id | Return department based on its ID |
| POST | /new | @RequestBody DepartmentRR request | Create new department |
I wanted to make +- functional delivery service, and delivery service main purpose is to deliver. But i have no real packages and other thing so we can simulate work of this system. For example me, Ivan Chekhanovskyi, want to send box of chocolate to my friend Jhon Doe. And lucky for us, we both have Delivery Departments in our areas. So mission is simple - i come to my post department, give them package and money, post workers deliver my package to Jhon's department, and he can receive it when it come's. Easy!
User register in delivery system, login in his profile and create invoice online.
User come's to department with his package. Worker check ID of that package. If he find that created invoice and all data is fine, he take the package, mark's it and send it to shipment storage. If some data is wrong or invoice is not created, he can create it by himself.
When package is ready to deliver, another worker with his portable device (phone or something, idk) scans package - it status automatically marks as DELIVERY-IN-PROGRESS (in our case we cant, scan package, but we can find it by id and change status manually). After scan worker load package to transport.
When package arived to destination department and worker unload all packages, he scan every package with his device. (Basicaly same process ans Step 3 but in revers)
Jhon see in his dashboard that package is delivered and he comes to department to receive it. In department he say worker his name or phone to identify that he is the person for whom this package. When worker confirm that it's the person i send package to, he change status of package as RECEIVED, and give package to recipient.
For that project i use relative database PostgreSQL. Currently used 4 tables:
- departments
- packages
- users
- workinghours
Workinghours table uses for defining department working hours.
