Rocket complex design, what should we do?

[IniterWorker]

Hi everyone,

I'm currently designing some kind of boilerplate. I implemented an authentication flow JWT token-based implemented over Request Guard and added OpenAPI/Swagger.

But, after reading all information available in the Rocket documentation, I didn't see any best practice to handle very complex design.

• https://github.com/SergioBenitez/Rocket/tree/master/examples
• https://rocket.rs/v0.5-rc/guide/state/#within-guards

I am wondering what's the best approach, with rocket.rs, to decoupling business logic, facilitating the testing and designing a robust solution. Of course, if you have any alternatives or hints, I will be grateful.

First thought:

My first thought is about using the FromRequest to build some kind of services/controller software design architecture.

I plan to use FromRequest to carry services and define routes as controllers that use these services.

• From the todo example, I saw some advantages for using the service out of the box to implement unit tests/integration tests. (I'm referring to the DB part of this example)
• Based on the last bullet point, I should consider that a service must be independent of FromRequest.

Let's say we have four services:

• The DB-Service (Db-Pool)
• The Auth-Service depends on DB-Service (login, register, ...)
• The A-Service depends on B-Service.
• The B-Service depends on DB-Service.

Questions:

1. Is Controller/Service a good design pattern for rocket.rs?
2. Is FromRequest, particularly the Request Guard, the best way to do it?
3. Should I use request guard with locale-state/cache as singleton/storage for the service instance (A-Service, ...)?

Best regards,