Rethinking the Rust and SQLite service architecture

I am torn between two options.

First, I could keep the Rust + SQLite service unchanged, though I expect scalability problems eventually.

Second, I might divide the service into two parts: a Rust worker handling API calls and a Rust + SQLite component acting as a serverless layer for the database.

The current instance would become two smaller instances linked by private IP.

Splitting the code could improve monitoring.

I am still weighing these choices.