YouCourse
Web-based e-learning platform with automated registration and payments, course management, and learner tracking.
Full Stack
TrackItAll.
Full-stack supply chain application covering procurement, production, and delivery, with role management and a secured REST API.
JavaSpring BootSpring Data JPAHibernateMySQLSpring AOPJUnitMockitoSwagger
GitHub
Problem
Supply chain work was split across procurement, production, and delivery without a shared contract. Teams needed one application for those modules, with clear roles and an API that could be tested and documented.
Solution
I built a full-stack Spring Boot application around the three modules, with JPA persistence, role-aware access, AOP for cross-cutting concerns, and a documented REST API covered by JUnit and Mockito tests.
TrackItAll is a supply chain management platform with Procurement, Production, and Delivery modules. User roles control access, and a secured, tested REST API sits behind the operational workflows. The stack is Java and Spring Boot with Spring Data JPA, MySQL, Spring AOP, JUnit, Mockito, and Swagger/OpenAPI.
Features
Procurement
Module for purchasing and inbound supply-chain operations.
Production
Module for tracking production work inside the same system.
Delivery
Module for outbound delivery workflows.
User roles
Role management so operational access stays separated.
Secured REST API
Authenticated endpoints with OpenAPI documentation.
Automated tests
JUnit and Mockito coverage around the service layer.
Architecture
A simplified view of the system and, where relevant, the delivery path.
Application
- REST API
- Spring Boot
- Spring Data JPA
- MySQL
Quality
- JUnit
- Mockito
- Swagger
Technical challenges
Challenge
Keep procurement, production, and delivery consistent without coupling every flow.
Solution
Separated modules around the same persistence model and shared only the identifiers and rules they needed.
Result
Each module can evolve without rewriting the whole chain.
Challenge
Ship a REST API that operators and future clients can trust.
Solution
Documented the contract with Swagger/OpenAPI and covered critical paths with unit tests.
Result
The API stays explicit, and regressions fail in CI instead of in production.
Technologies
JavaSpring BootSpring Data JPAHibernateMySQLSpring AOPJUnitMockitoSwagger
Screenshots
Lessons learned
- Supply chain modules stay maintainable when the API contract is designed before the controllers grow.
- Tests and OpenAPI documentation belong with the service, not after the first consumer arrives.
Related projects
Adjacent work in architecture, delivery, or interface design.