<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/event-sourcing-the-timeline-projector-yycbzzibt" -->

---
title: Event Sourcing: the Timeline projector | daily.dev
description: This final post in a series on event sourcing walks through the Timeline projector written in F# that turns bi-temporal events into timelines. It covers two...
canonical: https://daily.dev/posts/event-sourcing-the-timeline-projector-yycbzzibt
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Event Sourcing: the Timeline projector | daily.dev
og:description: This final post in a series on event sourcing walks through the Timeline projector written in F# that turns bi-temporal events into timelines. It covers two...
og:url: https://daily.dev/posts/event-sourcing-the-timeline-projector-yycbzzibt
og:image: https://api.daily.dev/og/posts/yYCBZzibt.png
og:image:alt: Event Sourcing: the Timeline projector
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.

# Event Sourcing: the Timeline projector

**[We Are .NET](https://daily.dev/sources/wearedotnet)** · 6 min read · 0 upvotes · 1 comments

## Summary

This final post in a series on event sourcing walks through the Timeline projector written in F# that turns bi-temporal events into timelines. It covers two configuration styles, CreateProjectionAction for create-update-delete timelines and SetProjectionAction for set-remove timelines, plus an OverrideBehavior setting for conflicting set events. The folder function builds timeline phases by folding over sorted events, and phases are built in reverse order because prepending is faster. Benchmark.NET was used to optimize the code, since the projector runs thousands of times per second. The author notes they built a custom solution because no .NET event sourcing libraries existed when they started, and lists questions to weigh before choosing a library over a custom build.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.planetgeek.ch/2026/11/17/event-sourcing-the-timeline-projector>

## Questions this post answers

### How do I decide whether to build a custom event sourcing projector or use an existing library?

Weigh database flexibility, whether bi-temporal events are common in your domain, and whether you are building a long-running product versus a short-lived project. A custom projector makes sense when you need bi-temporal timeline support that off-the-shelf .NET event sourcing libraries don't provide, since such libraries were largely unavailable or ill-suited when this particular system started.

_Comparing event sourcing libraries against a custom build is easier with real-world tradeoffs surfaced on daily.dev._

### Why would building timeline phases in reverse order be faster in F#?

Prepending an item to the front of an immutable list is faster than appending to the end, because F# lists are singly linked lists built by cons cells. Folding events and adding each new phase to the front avoids the cost of traversing or rebuilding the list, so the phases are accumulated in reverse and reversed once at the end.

_Developers optimizing F# data pipelines track performance tricks like this one on daily.dev._

## Community discussion

Top comments from developers on daily.dev.

**@nark3d** · 0 upvotes

> Ordering by kind so a Sets comes before a Changes at the same effective and application timestamp needs a tie-break the timestamps alone don't give you.  Two events that look simultaneous to the timestamps still have a right answer.  That's the kind of thing that only shows up as a flaky timeline months later.  Does the type documentation set that ordering out plainly, for whoever adds a new event kind next?

## Similar posts on daily.dev

- [Event Sourcing: fun with bi-temporal timelines](https://daily.dev/posts/event-sourcing-fun-with-bi-temporal-timelines-znsnieuys) · We Are .NET · 0 upvotes · 0 comments
- [Event Sourcing: A close look at the projector for values](https://daily.dev/posts/event-sourcing-a-close-look-at-the-projector-for-values-uqvtarhsm) · We Are .NET · 0 upvotes · 1 comments
- [Event Sourcing: set-and-remove-based bi-temporal events](https://daily.dev/posts/event-sourcing-set-and-remove-based-bi-temporal-events-8de56bzad) · We Are .NET · 1 upvotes · 0 comments
- [Event Sourcing: Is our Projection Code fast enough?](https://daily.dev/posts/event-sourcing-is-our-projection-code-fast-enough--dkncxcgxh) · We Are .NET · 0 upvotes · 0 comments
- [Event Sourcing: the not-so-simple bi-temporal basics](https://daily.dev/posts/event-sourcing-the-not-so-simple-bi-temporal-basics-t4ntaclgn) · We Are .NET · 0 upvotes · 0 comments

---

Tags: [#architecture](https://daily.dev/tags/architecture), [#.net](https://daily.dev/tags/.net)

[View this post on daily.dev](https://daily.dev/posts/event-sourcing-the-timeline-projector-yycbzzibt)

```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":"Event Sourcing: the Timeline projector","url":"https://daily.dev/posts/event-sourcing-the-timeline-projector-yycbzzibt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/event-sourcing-the-timeline-projector-yycbzzibt"},"datePublished":"2026-11-17T08:28:01.750Z","dateModified":"2026-11-17T08:28:51.745Z","description":"This final post in a series on event sourcing walks through the Timeline projector written in F# that turns bi-temporal events into timelines. It covers two...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5587ae12625b0bb9ca2a9a9f2e3b217e?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5587ae12625b0bb9ca2a9a9f2e3b217e?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"We Are .NET","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":"We Are .NET","logo":"https://media.daily.dev/image/upload/s--BsnVOa3i--/f_auto/v1718347410/logos/wearedotnet","url":"https://daily.dev/sources/wearedotnet"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/event-sourcing-the-timeline-projector-yycbzzibt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"architecture,.net","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"We Are .NET","item":"https://daily.dev/sources/wearedotnet"},{"@type":"ListItem","position":3,"name":"Event Sourcing: the Timeline projector"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/event-sourcing-the-timeline-projector-yycbzzibt","comment":[{"@type":"Comment","text":"Ordering by kind so a Sets comes before a Changes at the same effective and application timestamp needs a tie-break the timestamps alone don’t give you.  Two events that look simultaneous to the timestamps still have a right answer.  That’s the kind of thing that only shows up as a flaky timeline months later.  Does the type documentation set that ordering out plainly, for whoever adds a new event kind next?","datePublished":"2026-11-19T17:24:25.593Z","url":"https://daily.dev/posts/yYCBZzibt#c-d8Ph6Z1nS","author":{"@type":"Person","name":"Adam","url":"https://daily.dev/nark3d","image":"https://avatars.githubusercontent.com/u/2162621?v=4"}}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/event-sourcing-the-timeline-projector-yycbzzibt#faq","mainEntity":[{"@type":"Question","name":"How do I decide whether to build a custom event sourcing projector or use an existing library?","acceptedAnswer":{"@type":"Answer","text":"Weigh database flexibility, whether bi-temporal events are common in your domain, and whether you are building a long-running product versus a short-lived project. A custom projector makes sense when you need bi-temporal timeline support that off-the-shelf .NET event sourcing libraries don't provide, since such libraries were largely unavailable or ill-suited when this particular system started. Comparing event sourcing libraries against a custom build is easier with real-world tradeoffs surfaced on daily.dev."}},{"@type":"Question","name":"Why would building timeline phases in reverse order be faster in F#?","acceptedAnswer":{"@type":"Answer","text":"Prepending an item to the front of an immutable list is faster than appending to the end, because F# lists are singly linked lists built by cons cells. Folding events and adding each new phase to the front avoids the cost of traversing or rebuilding the list, so the phases are accumulated in reverse and reversed once at the end. Developers optimizing F# data pipelines track performance tricks like this one on daily.dev."}}]}
```

