Role: Lead Software Engineer

The primary goal of this project was to design, develop, and deploy a robust fleet management system for Eonsfleet that would support fleet operators in streamlining their operations, managing assets, and optimizing efficiency. This initial MVP was built on a monolithic architecture with the future goal of transitioning to a microservices-based architecture to accommodate scaling and modularity.

The project was developed for Eonsfleet, an organization focused on providing innovative fleet management solutions to businesses. As the lead software engineer, I was responsible for overseeing the entire technical aspect of the project—from conceptualizing the architecture to ensuring smooth deployment. The purpose of the project was to create a flexible and scalable fleet management SaaS platform that organizations could rely on to manage vehicles, track resources, and handle operations effectively.

Eonsfleet needed a solution to help fleet managers efficiently track vehicles, manage fuel consumption, monitor driver performance, and optimize routes, among other operational challenges. The existing solutions in the market were either too rigid or lacked scalability to meet the growing demands of businesses.

To address these challenges, I led the team in designing a monolithic MVP that would serve as a solid foundation for fleet management operations. The key features included:

Real-time vehicle tracking

User management with access control

A fuel management system

Comprehensive reporting and analytics

Expenses management system

Driver management

Requisition management

Asset management

I structured the project using Laravel for backend development and React/React Native for the frontend to create a smooth, responsive user experience across devices. Laravel Sanctum was employed for secure user authentication, ensuring a safe multi-user environment.

We implemented subscription plans tailored for different organizational needs, enabling a modular approach to service delivery. Plan 1 included tracking and user management, while Plan 2 extended functionality with additional features like the operation hub.

This project reinforced the importance of developing a solution that balances initial simplicity with long-term scalability. Working within a monolithic architecture allowed us to quickly iterate and launch the MVP, but as the product evolved, I recognized the necessity of transitioning to a microservices architecture to better manage scaling, updates, and independent module development.

While the monolithic approach helped us deliver the MVP swiftly, I would advocate for designing the system with a microservices approach from the start if I had to do it again. This would prevent the challenges of refactoring later and enable smoother scalability as the project grows. Additionally, I would focus more on implementing CI/CD pipelines earlier in the development process to streamline deployment and testing.