Hi everyone,

I’m looking for some feedback on my capstone project for a Rust bootcamp. The project is RouteForge, a backend system that turns a day's parcel orders into optimized courier routes and spreads the search across horizontally scalable solvers.

I built this to dive deep into async Rust, concurrent worker patterns, and domain modeling.

Overview

RouteForge combines a robust PostgreSQL job queue, an actix-web API with real-time SSE progress tracking and a Leaflet visualization frontend, fault-tolerant worker solvers using heuristic algorithms like simulated annealing and 2-opt, and a companion Telegram bot.

I would greatly appreciate any feedback on the code structure, database patterns, concurrency handling, Rust idiomatic practices, or architectural improvements I can make.

The code is available here: [RouteForge]

Thanks in advance for taking a look!

2 posts - 2 participants

Read full topic