--- title: Stream ids, event types prefixes and other event data... description: When designing event schemas in event sourcing systems, developers often consider removing redundant data like stream IDs, entity prefixes in event type names,... canonical: https://daily.dev/posts/stream-ids-event-types-prefixes-and-other-event-data-you-might-not-want-to-slice-off-zzrdhwyi6 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Stream ids, event types prefixes and other event data you might not want to slice off | daily.dev og:description: When designing event schemas in event sourcing systems, developers often consider removing redundant data like stream IDs, entity prefixes in event type names,... og:url: https://daily.dev/posts/stream-ids-event-types-prefixes-and-other-event-data-you-might-not-want-to-slice-off-zzrdhwyi6 og:image: https://api.daily.dev/og/posts/zzrDHwyI6.png og:image:alt: Stream ids, event types prefixes and other event data you might not want to slice off 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. # Stream ids, event types prefixes and other event data you might not want to slice off **[Event-Driven by Oskar Dudycz](https://daily.dev/sources/event-driven-io)** · 8 min read · 0 upvotes · 0 comments ## Summary When designing event schemas in event sourcing systems, developers often consider removing redundant data like stream IDs, entity prefixes in event type names, and timestamps — since event stores store this metadata separately. The author argues against over-trimming event data: timestamps in event metadata represent system time, not business time, which can cause correctness issues and migration headaches. Removing entity IDs from event data sacrifices explicitness and makes events harder to understand in isolation, especially when used for read models or cross-module integration. Shortened event type names also break convention-based mapping. The recommendation is to keep events self-explanatory and close to the business process, even at the cost of some redundancy. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [Event Sourcing: You better Prevent long event streams](https://daily.dev/posts/event-sourcing-you-better-prevent-long-event-streams-ebtbewtn0) · We Are .NET · 0 upvotes · 0 comments - [Developers' tips for Event Sourcing & EDA](https://daily.dev/posts/developers-tips-for-event-sourcing-eda-9ezyc9slp) · Event Store · 0 upvotes · 0 comments --- Tags: [#architecture](https://daily.dev/tags/architecture), [#typescript](https://daily.dev/tags/typescript), [#domain-driven-design](https://daily.dev/tags/domain-driven-design) [View this post on daily.dev](https://daily.dev/posts/stream-ids-event-types-prefixes-and-other-event-data-you-might-not-want-to-slice-off-zzrdhwyi6) ```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":"Stream ids, event types prefixes and other event data you might not want to slice off","url":"https://daily.dev/posts/stream-ids-event-types-prefixes-and-other-event-data-you-might-not-want-to-slice-off-zzrdhwyi6","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/stream-ids-event-types-prefixes-and-other-event-data-you-might-not-want-to-slice-off-zzrdhwyi6"},"datePublished":"2026-06-17T11:25:59.977Z","dateModified":"2026-06-17T11:30:59.208Z","description":"When designing event schemas in event sourcing systems, developers often consider removing redundant data like stream IDs, entity prefixes in event type names,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c7647a5bf24f081b0b3ddf2b831b6990?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c7647a5bf24f081b0b3ddf2b831b6990?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Event-Driven by Oskar Dudycz","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":"Event-Driven by Oskar Dudycz","logo":"https://media.daily.dev/image/upload/s--unDKCFQ0--/f_auto,q_auto/v1781695550/logos/event-driven-io?_a=BAMAMiWQ0","url":"https://daily.dev/sources/event-driven-io"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/stream-ids-event-types-prefixes-and-other-event-data-you-might-not-want-to-slice-off-zzrdhwyi6","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"architecture,typescript,domain-driven-design","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Event-Driven by Oskar Dudycz","item":"https://daily.dev/sources/event-driven-io"},{"@type":"ListItem","position":3,"name":"Stream ids, event types prefixes and other event data you might not want to slice off"}]} ```