dmalusev / malusev998 Goto Github PK

Every website/blog needs some kind of database, mine is no exception. Previous website used PostgreSQL ans it's primary database. It served me very well and my plan is to continue to use it in this rewrite.
After some research for database drivers, a few really good ones popped onto the scene.

1. Diesel

2. tokio-postgres

3. sea-orm

4. Sqlx

5. I really wanted to try Diesel but it had one flow, it is not async, which is kind of a deal braker as I intended to run my API on a single CPU instance on Digital Ocean Cloud. Having no async support and having to block the executing thread will degrade performance for my API even if my traffic is low.

6. Tokio-Postgres is async library for postgres and tokio, as the name suggests, and since I'm using tokio as my future executor, this would be a really good choice, but it had one flow, no compile time query execution.

7. SeaORM - It's quite new

8. SQLx, Does all the things mentioned above and it's well maintained and documented with examples.

My Choice: SQLx

Setup axum for integration testing

Find a way to integrate dependencies into the axum framework. (App State)

After writing initial setup for config and logging, some limitations have been found.
Namely, configuration path is current set to the current executable path, this is not ideal for
production environment and docker deployment. Ideally configuration path should be received from command line argument like:

api --config-path=/etc/api/config.toml

Overriding configuration path is all well and good, but must not make development slower, so the propose is to generate default paths for dev, release and dist profiles defined in cargo
e.g.

Dev, Release:

./config.toml
Having configuration file in the same directory as the codebase is really nice to work with.

Dist:
/etc/api/config.toml
Since dist cargo profile is meant to be run in Linux environment (preferably in Container) is will be nice to set default value where container expects to find configuration.

Many more flags could come at the later stage of the product development, so bringing library like clap will be beneficial.

GitHub actions for building and testing API