--- title: A new architecture for Rust monorepos | daily.dev description: A proposed alternative architecture for Rust monorepos that groups crates by service/program context rather than using a flat list of prefixed package names.... canonical: https://daily.dev/posts/a-new-architecture-for-rust-monorepos-wsqvgznbt twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: A new architecture for Rust monorepos | daily.dev og:description: A proposed alternative architecture for Rust monorepos that groups crates by service/program context rather than using a flat list of prefixed package names.... og:url: https://daily.dev/posts/a-new-architecture-for-rust-monorepos-wsqvgznbt og:image: https://api.daily.dev/og/posts/WSqvGzNbt.png og:image:alt: A new architecture for Rust monorepos 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. # A new architecture for Rust monorepos **[Sylvain Kerkour](https://daily.dev/sources/kerkour)** · 1 min read · 0 upvotes · 0 comments ## Summary A proposed alternative architecture for Rust monorepos that groups crates by service/program context rather than using a flat list of prefixed package names. Program-specific crates are nested inside their parent service directory, while shared crates live in a common or libs folder. The author argues this grouping by domain context is better for both humans and coding agents. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is a good folder structure for a Rust monorepo with multiple services? One approach is to nest service-specific crates inside the main crate directory for each service, and place shared crates in a top-level common or libs folder. For example, myservice-server/ contains its own core/, database/, and other sub-crates, while myservice-cli/ holds its own sub-crates. This groups code by domain context rather than producing a flat list of prefixed package names. _Rust developers structuring multi-service repos discuss layout trade-offs like this on daily.dev._ ## Similar posts on daily.dev - [A Vision for Cargo](https://daily.dev/posts/a-vision-for-cargo-9f2kssnoj) · Lobsters · 1 upvotes · 0 comments - [Guideline: Rust Style](https://daily.dev/posts/guideline-rust-style-rxs5ftv9c) · Lobsters · 4 upvotes · 0 comments - [crates.io: development update](https://daily.dev/posts/crates-io-development-update-7smw22f99) · Rust · 11 upvotes · 0 comments - [A Monorepo Is NOT a Monolith](https://daily.dev/posts/a-monorepo-is-not-a-monolith-bl4utxeac) · Nx · 98 upvotes · 8 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/a-new-architecture-for-rust-monorepos-wsqvgznbt) ```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":"A new architecture for Rust monorepos","url":"https://daily.dev/posts/a-new-architecture-for-rust-monorepos-wsqvgznbt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/a-new-architecture-for-rust-monorepos-wsqvgznbt"},"datePublished":"2026-08-11T08:55:30.115Z","dateModified":"2026-08-11T09:24:39.229Z","description":"A proposed alternative architecture for Rust monorepos that groups crates by service/program context rather than using a flat list of prefixed package names....","image":"https://media.daily.dev/image/upload/s--1KxV4ohY--/f_auto/v1722860400/public/Placeholder%2007","thumbnailUrl":"https://media.daily.dev/image/upload/s--1KxV4ohY--/f_auto/v1722860400/public/Placeholder%2007","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/a-new-architecture-for-rust-monorepos-wsqvgznbt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"general-programming,rust","timeRequired":"PT1M"} {"@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":"A new architecture for Rust monorepos"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/a-new-architecture-for-rust-monorepos-wsqvgznbt#faq","mainEntity":[{"@type":"Question","name":"What is a good folder structure for a Rust monorepo with multiple services?","acceptedAnswer":{"@type":"Answer","text":"One approach is to nest service-specific crates inside the main crate directory for each service, and place shared crates in a top-level common or libs folder. For example, myservice-server/ contains its own core/, database/, and other sub-crates, while myservice-cli/ holds its own sub-crates. This groups code by domain context rather than producing a flat list of prefixed package names. Rust developers structuring multi-service repos discuss layout trade-offs like this on daily.dev."}}]} ```