Backend development cheat sheet (Rust)

1. 1Rust essentials for the backendThe parts of Rust that shape every service: ownership, enums and Result, traits, Cargo, async on Tokio, shared state, and the Axum and SQLx crates most APIs start from.9 concepts

   1. 1Ownership and borrowingEvery value has one owner and is dropped when the owner goes out of scope.
   2. 2Structs, enums and pattern matchingStructs group named fields.
   3. 3Result, Option and the ? operatorA function that can fail returns Result<T, E>, and a value that may be missing is an Option<T>.
   4. 4Traits and genericsA trait lists methods a type promises to have, implemented with impl Trait for Type.
   5. 5Cargo, crates and featuresCargo builds, tests and runs Rust code.
   6. 6async/await on TokioAn async function returns a future, which does nothing until it is awaited.
   7. 7Shared state: Arc, Mutex, Send and SyncArc<T> shares one value between tasks by counting references, and Mutex<T> or RwLock<T> lets them change it one at a time.
   8. 8Axum routers, extractors and IntoResponseAn Axum handler is an async function whose arguments are extractors: Path, Query, Json and State pull typed values out of the request.
   9. 9SQLx: checked queries and a poolSQLx runs plain SQL asynchronously.

   9 in this chapterOpen this chapter
2. 2Terminal and GitThe two tools every backend task starts with: moving around a machine in a shell, and keeping every change in version control.3 concepts

   1. 1Terminal essentialsA shell runs commands such as cd, ls, cat, grep and curl, and pipes (|) feed one command's output into the next.
   2. 2Git commits and branchesGit records snapshots of your project as commits.
   3. 3Pull requestsA pull request proposes merging a branch into main and shows the diff, CI results and review comments in one place.

   3 in this chapterOpen this chapter
3. How HTTP worksWhat happens between a client and your server: finding it, connecting securely and exchanging requests and responses.6 conceptsOpens with credits
4. Relational databases and SQLModel data, query it by hand, index it for real queries, keep it consistent with transactions and understand what the ORM does for you.10 conceptsOpens with credits
5. Designing and building APIsTurn the database into a contract other programs rely on: resources, validation, errors, pagination, safe retries, versioning and documentation.10 conceptsOpens with credits
6. Authentication and API securityDecide who is calling and what they may do, store secrets safely and close the holes attackers try first.10 conceptsOpens with credits
7. Caching, queues and performanceMeasure first, then make the service fast: cache the right things, keep slow work out of the request path and use database connections wisely.10 conceptsOpens with credits
8. Testing, CI/CD and deploymentBuild the safety net that lets you change code without fear: tests against a real database, a pipeline on every push and a container you can deploy and roll back.10 conceptsOpens with credits
9. Architecture and reliabilityHow services are split, how they talk and how they fail, and the patterns that keep a system up and traceable when a dependency is slow or down.10 conceptsOpens with credits
10. 10Glossary, A to ZEvery concept in the sheet and the smaller terms it uses, in one list.172 terms

APIs, databases, auth, deploys.