planetgeek.ch

Category.NET

Small optimizations, large systems: removing allocations from Event Hubs partition key hashing

By Daniel Marbach
In .NET, C#, Cloud
3 months ago
6 Min read
S

TL;DR: Small code paths become expensive when cloud workloads execute them millions of times. The Azure Event Hubs partition key resolver is one of those paths. By removing temporary allocations from the partition-key encoding path, the Azure Event Hubs SDK reduced garbage collection pressure on a publishing hot path. I like performance work most when it starts with a boring question: why is this small method showing up so much? That question came up while looking at the Azure Event Hubs client...

Read on

Event Sourcing: Read Models to the rescue

By Urs Enzler
In .NET, Event Sourcing, F#
4 months ago
9 Min read
E

This is part three of my event sourcing series. In the first two posts, I showed you approaches that rely solely on projections. Now is the time to introduce read models to support all your query needs. And maybe, solve some performance issues as well. Of course, I’ll discuss the downsides of read models, too.

To finish this post, I’ll do a deep dive into a code example.

Read on

Event Sourcing: Simple is often enough

By Urs Enzler
In .NET, Event Sourcing, F#
4 months ago
7 Min read
E

This is the first post in a series about event sourcing. I’ll start with a very simple event sourcing implementation that is often good enough. Most of our event streams are implemented in this simple approach. In the following posts, the concepts will be extended to match additional requirements. I’ll touch on read models, consistency, long event streams, archiving, compensation, event skipping, lifetimes, and bi-temporal event sourcing. Every post will explain the concepts and our...

Read on

C# – F# Interop (2026 edition)

By Urs Enzler
In .NET, C#, F#
7 months ago
6 Min read
C

One of the great features of .NET is that you can mix its programming languages (C#, F#, VB.NET) in a single solution and that assemblies written in one language can call assemblies written in other languages. This is great, especially when starting with F#. A team does not need to switch everything at once, but can keep using the existing C# code and use Interop to call C# from F# or vice versa.In this article, we take a look at the Interop story in 2026. Spoilers: it works great.

Read on

Tests are Documentation, or are they?

By Urs Enzler
In .NET, C#, F#, Testing
April 9, 2025
4 Min read
T

Yesterday evening, I gave a workshop titled “To test, or not to test” at the Software Crafters Zürich Meetup. In the workshop, we gathered reasons to write tests: being confident that the code works, being confident that regressions can be prevented, helping to drive the implementation, and having documentation of the system. Interestingly, when I prepared the workshop, I forgot about the documentation aspect of the tests. Here is why and why it matters.

Read on

Your First day on the team = releasing Your first feature

By Urs Enzler
In .NET, F#, How we do, Today's random F# code
December 13, 2024
21 Min read
Y

Welcome to our team! Today is your first day, which means it’s the day you’ll release your first feature. You’ll see everything needed to design, implement, and release a feature in our system. We’ll touch on F# language features, our TDD style, and some architecture topics.

This blog post is part of the F# Advent Calendar 2024 (thanks, Sergey, for the organisation).

Read on
planetgeek.ch

Recent Posts