--- title: Scaling Rust codebases: Lessons learned organizing large... description: Practical guidance for scaling large Rust codebases, covering workspace organization, dependency management, and error handling patterns. Key recommendations... canonical: https://daily.dev/posts/scaling-rust-codebases-lessons-learned-organizing-large-projects-and-managing-errors-avuzruan8 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Scaling Rust codebases: Lessons learned organizing large projects and managing errors | daily.dev og:description: Practical guidance for scaling large Rust codebases, covering workspace organization, dependency management, and error handling patterns. Key recommendations... og:url: https://daily.dev/posts/scaling-rust-codebases-lessons-learned-organizing-large-projects-and-managing-errors-avuzruan8 og:image: https://api.daily.dev/og/posts/AVUZRUAn8.png og:image:alt: Scaling Rust codebases: Lessons learned organizing large projects and managing errors og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Scaling Rust codebases: Lessons learned organizing large projects and managing errors **[Sylvain Kerkour](https://daily.dev/sources/kerkour)** · 9 min read · 0 upvotes · 0 comments ## Summary Practical guidance for scaling large Rust codebases, covering workspace organization, dependency management, and error handling patterns. Key recommendations include using Cargo workspaces with workspace-level dependency declarations, flattening package folder structures, keeping mod.rs and lib.rs files free of logic, and providing Makefiles and dev containers. For error handling, the post advocates a two-tier approach: a global errs::Error enum for cross-context propagation and local domain-specific Error types with From implementations, enabling centralized error handling at the presentation layer. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How should I organize errors across multiple crates in a large Rust workspace? Use a two-tier error system: define a global errs::Error enum with generic variants (NotFound, Internal, PermissionDenied, etc.) in a shared crate, and let each service or bounded context define its own fine-grained local Error type. Implement From for errs::Error so the ? operator converts errors at service boundaries. Public service methods always return errs::Error, never the local type, preventing internal error details from leaking across contexts. _Rust teams managing multi-crate error boundaries find patterns like this on daily.dev._ ### How do I declare shared dependency versions across all crates in a Cargo workspace? Declare dependencies in the workspace root Cargo.toml under [workspace.dependencies] with the version and features you want pinned. In each member crate's Cargo.toml, reference them with something = { workspace = true }. This keeps all crate versions synchronized and gives you a single inventory of third-party packages, eliminating version drift across a large workspace. _Developers maintaining large Rust workspaces track dependency management practices like this on daily.dev._ ### Should I avoid putting code in mod.rs and lib.rs files in Rust? Yes — keep mod.rs and lib.rs files exclusively for visibility declarations (pub use, pub mod), and put actual logic in descriptively named files like client.rs, payments.rs, or email.rs. When a project grows to hundreds of modules, having thousands of files all named mod.rs or lib.rs makes file-search in editors nearly useless, since every result looks identical. _Rust developers refactoring growing codebases share structural lessons like this on daily.dev._ ## Similar posts on daily.dev - [Guideline: Rust Style](https://daily.dev/posts/guideline-rust-style-rxs5ftv9c) · Lobsters · 4 upvotes · 0 comments - [Medium](https://daily.dev/posts/medium-j5k11rvds) · Medium · 0 upvotes · 0 comments - [Practical Rust API Design](https://daily.dev/posts/practical-rust-api-design-qwmqrnfyi) · corrode · 47 upvotes · 7 comments --- Tags: [#general-programming](https://daily.dev/tags/general-programming), [#rust](https://daily.dev/tags/rust) [View this post on daily.dev](https://daily.dev/posts/scaling-rust-codebases-lessons-learned-organizing-large-projects-and-managing-errors-avuzruan8) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Scaling Rust codebases: Lessons learned organizing large projects and managing errors","url":"https://daily.dev/posts/scaling-rust-codebases-lessons-learned-organizing-large-projects-and-managing-errors-avuzruan8","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/scaling-rust-codebases-lessons-learned-organizing-large-projects-and-managing-errors-avuzruan8"},"datePublished":"2026-08-11T08:56:25.086Z","dateModified":"2026-08-11T09:31:04.522Z","description":"Practical guidance for scaling large Rust codebases, covering workspace organization, dependency management, and error handling patterns. Key recommendations...","image":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","thumbnailUrl":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","isAccessibleForFree":true,"articleSection":"Sylvain Kerkour","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Sylvain Kerkour","logo":"https://media.daily.dev/image/upload/s--3ngWt4Yp--/f_auto,q_auto/v1786438308/logos/kerkour?_a=BAMAMicg0","url":"https://daily.dev/sources/kerkour"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/scaling-rust-codebases-lessons-learned-organizing-large-projects-and-managing-errors-avuzruan8","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"general-programming,rust","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Sylvain Kerkour","item":"https://daily.dev/sources/kerkour"},{"@type":"ListItem","position":3,"name":"Scaling Rust codebases: Lessons learned organizing large projects and managing errors"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/scaling-rust-codebases-lessons-learned-organizing-large-projects-and-managing-errors-avuzruan8#faq","mainEntity":[{"@type":"Question","name":"How should I organize errors across multiple crates in a large Rust workspace?","acceptedAnswer":{"@type":"Answer","text":"Use a two-tier error system: define a global errs::Error enum with generic variants (NotFound, Internal, PermissionDenied, etc.) in a shared crate, and let each service or bounded context define its own fine-grained local Error type. Implement From for errs::Error so the ? operator converts errors at service boundaries. Public service methods always return errs::Error, never the local type, preventing internal error details from leaking across contexts. Rust teams managing multi-crate error boundaries find patterns like this on daily.dev."}},{"@type":"Question","name":"How do I declare shared dependency versions across all crates in a Cargo workspace?","acceptedAnswer":{"@type":"Answer","text":"Declare dependencies in the workspace root Cargo.toml under [workspace.dependencies] with the version and features you want pinned. In each member crate's Cargo.toml, reference them with something = { workspace = true }. This keeps all crate versions synchronized and gives you a single inventory of third-party packages, eliminating version drift across a large workspace. Developers maintaining large Rust workspaces track dependency management practices like this on daily.dev."}},{"@type":"Question","name":"Should I avoid putting code in mod.rs and lib.rs files in Rust?","acceptedAnswer":{"@type":"Answer","text":"Yes — keep mod.rs and lib.rs files exclusively for visibility declarations (pub use, pub mod), and put actual logic in descriptively named files like client.rs, payments.rs, or email.rs. When a project grows to hundreds of modules, having thousands of files all named mod.rs or lib.rs makes file-search in editors nearly useless, since every result looks identical. Rust developers refactoring growing codebases share structural lessons like this on daily.dev."}}]} ```