Hello everyone,

When I started with Rust and Actix Web, I had quite a few questions about the framework, such as:

• How do I organize my code (handlers, models, routes, ... )?
• Which architecture to follow?
• How to manage the integration of Diesel?

Because unlike some frameworks such as Spring boot, Django, Rails, ... Actix does not offer a default structure, we have the freedom to structure it as we want.

So I wrote this article to propose a clear architecture because there aren't many of them in the Rust community.

Happy reading. Rust & Actix Web - Structure and Organizing an API like a pro

3 posts - 2 participants

Read full topic