Trying to solve a long-standing problem with @AkkaDotNET and automatic OTEL trace correlation

Looks like the core @AkkaDotNET repo hit 5000 stars today. Nice, thank you!

Full release notes here:

Happy 2026 everyone - our first release of the year, 1.5.58, is now out with some big fixes: - Fix .NET 10 CLR shutdown hook breaking change - Fix TCP listener crashes / restarts - Fix perf issues with semantic logging - Numerous other small bug fixes

I now have @AkkaDotNET actors running as part of the GitHub actions PR validation for the @petabridge website - using my link-validator tool to help us detect broken links before publication! Nice to do a bit of dogfooding

We get asked "how do I introduce Akka .NET actors into my legacy applications?" quite frequently from developers. In today's blog post we offer a direct answer to this question using some of our experiences working on Sdkbin's massive overhaul.

you can do this pretty trivially with @AkkaDotNET FWIW - actors can run anywhere.

Uses Akka .NET 👇

The core Akka .NET package has just passed 20m downloads! Also, crazy to think we just crossed ~100m org-wide downloads in late September and we've already grown our total install-base by 10% since then.

Fun breaking change in .NET 10 - this has an impact on @AkkaDotNET 's ability to gracefully exit clusters if you're running: 1. .NET 10 2. Not using Akka .Hosting We're going to get a fix for this out soon, but FYI

Release notes here:

Akka .NET v1.5.57 is out, which includes: 1. Semantic logging support by default 2. Async / await support inside Akka.Persistence callbacks, plus an "onComplete" callback handler that runs after all events in a batch have been persisted We're rolling this out to all libraries

Deployed latest the: @AkkaDotNET hosting beta, which runs with semantic logging built-in by default. Left is before, right is after. No code changes required. Semantic properties are now showing up automatically.

Akka .NET v1.5.57-beta1 is out - our first release with semantic logging support: https://t.co/MpHAGv5ICZ We are working on rolling this out to all of our logging plugins this week too.

New Video / Blog Post: "The Worst Security Vulnerability in Akka .NET - And How to Fix It" (we had a massive bug in our TLS implementation and fixed it back in October) 🔗 in next post

ASP .NET Core Server-Sent Events Pairs Wonderfully with Akka .NET Streams (a demonstration)

Most .NET devs on X argue about architecture practices for web apps that have 3 concurrent users max. So here's a story about how we helped a utility handle 1m concurrent meter connections safely using Akka .NET. This is the unseen "dark matter" stuff .NET powers everywhere

Solving the two most annoying API limitations with @AkkaDotNET persistence at the same time: 1. Persistence callbacks now support await internally 2. For `PersistAll`, you now have a handler that runs after the entire batch has been persisted

Our Nov 2025 Community Standup is scheduled for this Wednesday at 12pm Chicago time. Join us as we discuss: - Akka .NET Durable Reminders - mTLS improvements - Akka.Persistence health checks roll-out We will also honor the memory of our friend and core contributor @Danthar

No @AkkaDotNET Community Standup this week - we're going to postpone it until the 19th