jet/dotnet-templates
This system is a comprehensive library and template suite for building event-sourced .NET applications using the Equinox and Propulsion frameworks. It provides a collection of ready-to-use project templates that implement common architectural patterns, including reactive processing, data indexing, and stream consumption. The system supports multiple storage backends such as Cosmos DB, DynamoDB, and Kafka, enabling developers to quickly scaffold services for data ingestion, state management, and event projection.
66.2
Adequate · 29 July 2026
775
lines of production code
F#
with C#
1
bus factor · 12 authors in all
4
measurements over time
How it got here
2018–2019 · Equinox 4 and Propulsion 3 migration
This period focused on upgrading the codebase to .NET 8/10 and integrating Equinox 4 and Propulsion 3, which introduced new APIs for handling commands, queries, and serialization. The team expanded the template library with new tools for event sourcing, including Kafka consumers, projectors, and sync utilities, while refactoring existing web and domain layers to support multiple storage backends.
14 changes
2020–2023 · Expansion of Propulsion and Equinox templates
This period focused on expanding the framework's capabilities by introducing numerous new templates for event sourcing and processing, including the Propulsion reactor, archiver, pruner, and indexer, as well as the Equinox shipping and hotel samples. The work emphasized multi-source and multi-target support across various storage backends like Cosmos DB, DynamoDB, and Kafka, while also adding infrastructure for AWS CDK and integration tests to ensure template reliability.
12 changes
Survey your own repository
jet/dotnet-templates was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 29 July 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 9a44cd9de0 — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.