--- title: Resource Names for Enterprise TypeScript Monorepos description: Multi-service TypeScript monorepos often suffer from inconsistent resource naming — each team invents its own string interpolation patterns. Inspired by the... canonical: https://daily.dev/posts/resource-names-for-enterprise-typescript-monorepos-enplldi7g twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Resource Names for Enterprise TypeScript Monorepos | daily.dev og:description: Multi-service TypeScript monorepos often suffer from inconsistent resource naming — each team invents its own string interpolation patterns. Inspired by the... og:url: https://daily.dev/posts/resource-names-for-enterprise-typescript-monorepos-enplldi7g og:image: https://api.daily.dev/og/posts/enPlLdi7G.png og:image:alt: Resource Names for Enterprise TypeScript 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. # Resource Names for Enterprise TypeScript Monorepos **[Robin Wieruch](https://daily.dev/sources/robinwieruch)** · [@rwieruch](https://daily.dev/rwieruch) · 8 min read · 0 upvotes · 0 comments ## Summary Multi-service TypeScript monorepos often suffer from inconsistent resource naming — each team invents its own string interpolation patterns. Inspired by the Google API Design Guide, this post proposes treating resource names as first-class structured data with shared encode/decode utilities. Relative resource names follow a `collection/id` hierarchy, while full resource names prepend `//service.domain/` for cross-service identification. Resource types (`service.domain/TypeName`) handle 'what kind' of resource. A typed `ServiceName` union prevents typos at compile time, and domain-specific constants are constructed via `encodeResourceType` rather than hardcoded. The utilities live in a shared monorepo package, giving every service a single source of truth for resource identity. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [Enabling internationalization in our web Turbo monorepo](https://daily.dev/posts/enabling-internationalization-in-our-web-turbo-monorepo-cz52gwlcb) · Mercari Engineering · 2 upvotes · 0 comments --- Tags: [#general-programming](https://daily.dev/tags/general-programming), [#architecture](https://daily.dev/tags/architecture), [#typescript](https://daily.dev/tags/typescript), [#microservices](https://daily.dev/tags/microservices) [View this post on daily.dev](https://daily.dev/posts/resource-names-for-enterprise-typescript-monorepos-enplldi7g) ```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":"Resource Names for Enterprise TypeScript Monorepos","url":"https://daily.dev/posts/resource-names-for-enterprise-typescript-monorepos-enplldi7g","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/resource-names-for-enterprise-typescript-monorepos-enplldi7g"},"datePublished":"2026-03-30T11:48:52.738Z","dateModified":"2026-03-31T08:00:15.292Z","description":"Multi-service TypeScript monorepos often suffer from inconsistent resource naming — each team invents its own string interpolation patterns. Inspired by the...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c386fe675406adec4a79983622ceace8?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c386fe675406adec4a79983622ceace8?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Robin Wieruch","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":"Person","name":"Robin Wieruch","url":"https://daily.dev/rwieruch","image":"https://avatars.githubusercontent.com/u/2479967?v=4","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":1500}},"commentCount":0,"discussionUrl":"https://daily.dev/posts/resource-names-for-enterprise-typescript-monorepos-enplldi7g","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"general-programming,architecture,typescript,microservices","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Robin Wieruch","item":"https://daily.dev/sources/robinwieruch"},{"@type":"ListItem","position":3,"name":"Resource Names for Enterprise TypeScript Monorepos"}]} ```