Rust Axum Production Coding – Rust Web Development

I learned a lot from your video！非常感谢！我要试着写一遍代码了！

This is awesome man! Pure gold content. Thanks for all the effort you've put making the app, explaining what you´re doing and editing the video!

Jeremy, another idea for this series would be implementing more Managers, services, etc, outside of ModelManager. Something like remote apis, because sometimes we need an external service request.
I'm building a backend in RUST with JSONRPC using your architecture and I'm struggling with how to struct differents managers and how to handle it inside my Rpc methods.

I know that with Axum we usually build an AppState that stores everything and pass it to our routes, but as we only have "one" route ("/rpc"), but different methods (task_create, task_update, etc), not always we'ill use everything the AppState provides. For example, let's suppose that `method_a` uses XManager, `method_b` only uses YManager and `method_c` uses both of them.
With a linear search it can be managed very well, but the problem comes when you try to implement a registration to the rpc methods.

I think that will show very well the use of traits, generics, futures handling, project structures, etc.

Thanks for the videos!

Hello, I'm having some trouble with postgres start up. I clone github rep and run commands in the README:
– cargo watch -q -c -w src/ -w .cargo/ -x "run"
– docker run –rm –name pg -p 5432:5432 -e POSTGRES_PASSWORD=welcome postgres:15

Code panicked at unwrap:
INIT.get_or_init(|| async {

info!("{:<12} – init_dev_all()", "FOR-DEV-ONLY");

dev_db::init_dev_db().await.unwrap(); // <<<<< HERE

})

Saying: "thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Database(PgDatabaseError { severity: Fatal, code: "28P01", message: "password authentication failed for user "postgres"", …… , file: Some("auth.c"), line: Some(285), routine: Some("auth_failed") })', src_dev_utilsmod.rs:21:37"

When I inspect container, there is indeed env POSTGRES_PASSWORD = welcome.

I literally just did what Jeremy did, so I'm hopeless.
Some ideas on how to fix it? Thank you.

Jeremy, about the tests for Bmc (TaskBmc), I came across an error with tokio runtime. It seems that running some tests together crash the runtime and some tests fail randomly. Did it happen with you?

An error message example:

running 4 tests
test model::user::user_bmc_tests::test_get_err_not_found … ok
test model::user::user_bmc_tests::test_delete_err_not_found … ok
test model::user::user_bmc_tests::test_get_ok … ok
test model::user::user_bmc_tests::test_update_ok … FAILED

failures:

—- model::user::user_bmc_tests::test_update_ok stdout —-
thread 'model::user::user_bmc_tests::test_update_ok' panicked at 'assertion failed: `(left == right)`
left: `0`,
right: `1`', /Users/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/io/scheduled_io.rs:220:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This is such an amazing resource! I am new to “production” API architecture and I was just wondering where I can read more about this particular architecture? (Web, context, event, model etc). Or if you have any resources for other API architectures you like. Keep up the absolutely spectacular work

Why rust is so difficult 😢.

Great video Jeremy. About the JSONRPC, you did a linear search approach. What about a project with alot of namespaces and methods? What's the best way to handle every possible method?

Really nice video ! I really like all the explaination on why we do things like these instead of another manner. I started to improve the project on my side so that i will compare with your solution on the next videos, i started with tracing and exposing metrics for prometheus. I juste have a questions about the model layer. I am not a big fan of ORM but for nested entities I didn't found good implementations to do it with sqlx. What are you thoutgh on that, do you have any ressources that could help me ?

Thank you a lot for the videos and your contribution to the Rust community as a whole.

Small suggestions:
– "thiserror" crate instead of implementing the Error boilerplate
– "clap" crate for the configuration part

Fantastic video! So glad that I found you since I am learning rust and do not have that much web/server experience. Found a lot of things that I can improve in my axum server. Keep it up, instantly subscribed!

Incredible, every time ❤

1:36:45 in this chapter you use sqlb crate to build sql queries, why not use something like diesel or sea-orm for this ? what downsides to using orm instead of direct sql queries?
great series btw, very nice video.

thank you, learnt alot from you! I love the way you teach, easy to follow. did not expect I can finish in a session.

Fantastic ❤

The best video of AXUM !

Hi Jeremy. It is so nice to see another of your courses. Hopefully i will find the time soon to follow you. lf 2 it. keep up the good work

You can really feel the passion and the amount of dedication that went into this. Very unique here on YouTube. I hope you'll continue to be able to produce high quality content like this full time. ❤

I never comment on YouTube, this is a masterpiece, thank you, you made the difference.

Great video! Looking forward to the next one.

So much wisdom condensed in one place! Also, that .cargo/config.toml trick is really neat!

Your videos and explanations are amazing. It would be really great to see integrations when it comes to auth for this example with real world providers developers use like auth0, azure or other oauth providers.

Will you make a video about deploying Rust applications as well? That would be great as a last part to this series.

Really cool! ❤

Great video- learned a lot

Thanks, well done Jeremy 👍🙌

This video needs a lot more attention.

The way this was explained…. WoW 👏👏👏👏👏👏