Replace warp with axum

[mickvandijke]

• API overhaul: reimplement the current API using Axum #143
• Reimplement the current HTTP tracker using Axum #160

[da2ce7]

@josecelano suggested that we might want to consider Rocket. From the looks of it, it seems really cool!

https://github.com/SergioBenitez/Rocket/tree/master

[da2ce7]

In addition, by the same primary author as Rocket, there is Figment, for managing the configuration the application.

[mickvandijke]

@josecelano suggested that we might want to consider Rocket. From the looks of it, it seems really cool!

https://github.com/SergioBenitez/Rocket/tree/master

Hey @da2ce7 @josecelano ,

Rocket's documentation does look really nice, but the project still has a long way to go to compete with other webserver frameworks in Rust in terms of performance: https://web-frameworks-benchmark.netlify.app/result?asc=0&l=rust&metric=totalRequestsPerS&order_by=level512.

[da2ce7]

@josecelano suggested that we might want to consider Rocket. From the looks of it, it seems really cool!
https://github.com/SergioBenitez/Rocket/tree/master

Hey @da2ce7 @josecelano ,

Rocket's documentation does look really nice, but the project still has a long way to go to compete with other webserver frameworks in Rust in terms of performance: https://web-frameworks-benchmark.netlify.app/result?asc=0&l=rust&metric=totalRequestsPerS&order_by=level512.

The difference seems to be about 50% of the speed of the competition. - This isn't so devastating. Using a better and more correct interface is of significant advantage. Optimization for speed can always be preformed later.

[Power2All]

@josecelano suggested that we might want to consider Rocket. From the looks of it, it seems really cool!
https://github.com/SergioBenitez/Rocket/tree/master

Hey @da2ce7 @josecelano ,
Rocket's documentation does look really nice, but the project still has a long way to go to compete with other webserver frameworks in Rust in terms of performance: https://web-frameworks-benchmark.netlify.app/result?asc=0&l=rust&metric=totalRequestsPerS&order_by=level512.

The difference seems to be about 50% of the speed of the competition. - This isn't so devastating. Using a better and more correct interface is of significant advantage. Optimization for speed can always be preformed later.

Sadly, performance is the crux when it comes to trackers.
Currently, I've got my own project based on Torrust-Tracker, and it's already straining with using Axum, let stand using Rocket where I could literally keelhaul my server.

[josecelano]

Done.