This project is designed to solve a drone delivery optimization problem, where each drone can carry a certain weight and deliver packages to multiple locations. The main aim is to minimize the number of trips required by each drone to complete all deliveries. This is essential, as each time a drone returns to the home base, refueling and reloading costs are incurred.
This application is automatically deployed using GitHub Actions and is hosted on Azure.
- Backend: .NET 6, C# 10
- Testing: xUnit 2.4.2
- Frontend: Blazor with Radzen.Blazor 4.18.1
- Domain: Contains all the domain entities (Drone and Location).
- Application (UseCases): Handles the business logic and use cases.
- Presentation: Holds the front-end and API logic.
Two types of delivery strategies have been implemented:
- No Travel Time: Focuses on reducing the number of trips by using the drone with the highest payload capacity.
- Has Travel Time: Considers a fixed travel time for each drone and aims to distribute the deliveries across multiple drones concurrently.
You can toggle between these strategies when hitting the endpoint.
- Restore all NuGet packages.
- Build the project.
- Run the .Server project.
- Execute unit tests to verify everything is working as expected.
Unit tests are available in the Application layer to ensure the logic is working correctly.
- Keep the code as DRY as possible.
- Proper indentation for readability.
- Stick to the SOLID principles and clean architecture.
Used for decoupling the components, making it easier to use cases calls. It simplifies the code structure and makes it more maintainable.
It improves the user experience converting text into a format that's easier to read and understand.
Chosen for unit testing to write more expressive assertions. Makes the tests easier to read and understand.
Employed for mocking objects in unit tests. It isolates the code under test, making sure external dependencies don't affect the outcomes.