Best Practices for Using SQLx in a Multi-Crate Project with a Single Database

[t-ce]

Hi everyone,

I’m currently developing a multi-crate Rust proof-of-work application using SQLx and Actix-web, organized as a workspace that includes the following crates: main-app, finance, sales, and common. The finance and sales crates will each manage their own database migrations, ideally organized in directories like finance/migrations and sales/migrations.

At the project root, I have a docker-compose.yml file along with a .env file that contains the DATABASE_URL. Both the finance and sales crates will connect to a single database instance.

I would greatly appreciate any guidance on the idiomatic way to implement migrations for each crate in this setup. Additionally, I’m seeking advice on how to effectively configure Visual Studio Code to work with this multi-crate structure, ensuring that it recognizes the migrations and database connections appropriately.

Thank you in advance for your assistance!

P.S. I haven’t come across any blogs that cover this topic (Modularization of Database Models/Separation of Concerns in Database Design/Rust SQLx Migration Patterns), which seems like a significant oversight for any non-trivial project. If you have any links to relevant resources or articles, I would be very grateful!