Application architecture split into crates

[SZenglein]

Hey, thanks for loco, IMHO it made a lot of really good decisions and I look forward to trying it out.

Is it possible to structure my application so that different parts are split into their own crates? Basically I want to do an architecture similar to a microservice architecture but all run under the same application (but easily reusable or refactored).

I'm thinking ´Hooks` is a good starting point. Similar to how an axum router can nest another router, I want my app to nest another app that also exposes background tasks etc.

There are some issues around this like taking care migrations do not conflict or how to handle authentication, but I'm interested in general feasibility of this idea. Maybe you can help :).

[thaarrtt]

I dont think loco fit with microservice since the main purpose is to be one person framework

[SZenglein]

Thanks for you response! My primary concern is the necessity to put everything into one huge crate. Apart from slow compile times, I have found that a project with many modules easily becomes difficult to maintain after growing for a while.

I noticed that it is common for us that a module usually has its own child-router and database objects. Making it too easy to directly depend on "foreign" sea-orm entities can make refactors very difficult.

But I guess loco really might not be the best fit for such an architecture.

[thaarrtt]

for nest functionality, I basically using hack like this since AppRoutes loco provide is "simple"

then you can use v1,v2 then resources like payment admin,payment user something like that