How much interested would there be in a series of blog posts on how to build a production-ready(ish) API in @rustlang from scratch?
Think database setup, domain layer, API layer, non-functional requirements (logging, tracing, metrics), integration tests, benchmarks, etc.
-
Show this thread
-
Replying to @algo_luca @rustlang
does "from scratch" mean "I'm gonna use 50 crates"? Or like actually from scratch?
1 reply 0 retweets 0 likes -
Not 50, but probably a good handful of them. Re-implementing every component is out of the scope of the project - we will be using what is available in the ecosystem when possible, rolling our own where needed. Contributing upstream if indeed useful outside of the course itself.
1 reply 0 retweets 1 like -
Replying to @algo_luca @rustlang
Shame. I think that education which delves into how the lower level parts of a tech stack work is the most important to focus on. Particularly in this early era of Rust when we still don't know the best abstractions to have and we need people to be experimenting a lot.
1 reply 0 retweets 0 likes -
Re-implementing pieces of the stack is extremely useful, but you wouldn't naively deploy your own crypto to production and the same applies to an HTTP client or a web server. This guide will be geared towards production users.
1 reply 0 retweets 2 likes
I'd be more than happy to read pieces delving deep in how each of those components work, but it's too broad of a scope for what I am setting out to do here :)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Writing about stuff to learn how it works, mostly in Rust.
Lead Engineer at