LogiFlow — Backend-Driven Logistics Management Platform

LogiFlow is a full-stack logistics management system designed to simulate real-world heavy freight operations. The platform manages container workflows, driver allocation, compliance monitoring, and real-time tracking across web and mobile clients.

Developed as a team project, where I led the backend architecture and infrastructure design.

👤 My Role & Backend Ownership

In this project, I was responsible for designing and implementing the entire backend foundation, including:

• Architecture Lead: Designed the layered structure and established backend standards for the team.
• Security & Auth: Designed JWT-based stateless authentication and Spring Security configuration with role-based authorization.
• Database Schema: Designed the database schema and managed complex entity relationships (OneToMany, ManyToOne).
• Infrastructure: Implemented centralized exception handling and structured the service layer to ensure business logic remains isolated from API contracts.

Other team members built application features and client interfaces on top of the backend architecture I established.

🧱 System Architecture

The backend follows a layered architecture inspired by production practices: Controller → Service → Repository → Database

The system is designed with a layered backend architecture and stateless authentication to support scalability and maintain a clean separation of concerns.

Key Design Decisions

• Separation of Concerns: Business logic is strictly isolated in the service layer, while controllers manage HTTP request/response cycles.
• DTO Pattern: Used to prevent exposing internal domain models and maintain clean, stable API contracts.
• Stateless Auth: Leveraged JWT to allow horizontal scalability without server-side sessions.
• RBAC: Role-based access control via Spring Security filters to ensure secure operation across different user types.

🔐 Security & Auth Design

Secure Stateless Authentication

JWT-based authentication is used with Spring Security to enable stateless sessions and horizontal scalability. Role-based access control (RBAC) enforces authorization across Admin, Dispatcher, Driver, and Customer roles.

Credentials & Protection

Passwords are stored with BCrypt hashing. Sensitive external service credentials are externalized (properties/environment) to avoid embedding secrets in code.

Database & Relationship Design

Relational mappings (OneToMany, ManyToOne) include explicit constraints and cascade rules. Serialization and lazy-loading are handled carefully to avoid common JPA pitfalls.

External Integrations

Cloudinary, Tesseract OCR, Mistral AI, PayPal Sandbox, and SMTP are integrated through well-scoped adapters and externalized configuration to preserve modularity and security.

🌐 Core Capabilities

• Role-aware driver assignment workflow
• Container and cargo management
• Real-time tracking integration
• OCR-based document digitization (Tesseract)
• AI-powered logistics insights (Mistral AI)
• Secure payment processing (PayPal Sandbox)
• Automated email notifications (SMTP)
• Swagger API documentation

🛠 Tech Stack

Backend:

• Java 21
• Spring Boot 3.5+
• Spring Security
• PostgreSQL 15 (PostGIS support)
• Maven

Web Frontend:

• React 19 + Vite

Mobile:

• Flutter 3.9+

External Integrations:

• Cloudinary (File Storage)
• Tesseract OCR (Document Processing)
• Mistral AI (AI Features)
• PayPal Sandbox (Payments)

🏗 Project Structure

logiflow/
├── server/          # Spring Boot backend
├── client/          # React web application
└── client_mobile/   # Flutter mobile application

🚀 Production Hardening Roadmap

• Containerization with Docker: Build and publish container images for all services.
• CI/CD pipeline integration: Automate build, test, and deployment workflows.
• Centralized logging & monitoring: Implement aggregated logs, metrics, and alerting.
• Cloud deployment (AWS/Azure): Prepare infra-as-code and secure cloud deployments for production.

⚙️ Running Locally (Simplified)

1. Configure PostgreSQL: Ensure database is running and accessible.
2. Update Properties: Configure application.properties with database credentials and API keys for external services.
3. Run Backend: Start the Spring Boot application from the server directory.
4. Start Web Frontend: Navigate to client, run npm install and npm run dev.
5. Run Mobile Client (Optional): Open client_mobile in Android Studio/VS Code and run on an emulator/device.

Detailed configuration steps are available in the project folders.

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.