So @AkkaDotNET v1.6 is already an order-of-magnitude improvement for networking and serialization performance over v1.5, but the next beta of it is about to be even faster: Looking at about a ~20% throughput improvement across the board and significant reductions in CPU / mem resources per message. All from simple mechanical fixes plus some experimental IActorRef compression on the receiving side of the wire.

Had a customer try out @AkkaDotNET v1.6 in their high-performance app today and report several different performance / code-generated serializer issues their agents found while exercising it. The rate at which we can improve software now is just incredible

Going to do a for real post on this soon, but late last night we shipped @AkkaDotNET v1.6-beta1 This includes: - Full AOT support for core Akka, Hosting, Streams - Source-generated serialization + System.Memory-powered primitives for it + all I/O - Artery.Tcp - need to re-benchmark it since Iast posted about it but TL;DR; it can do 1.6m msg/s over a single connection, and these are REAL message payloads, not byte arrays or strings. I've already validated the AOT support in a live application that consumes Akka + Akka.Streams - works great so far. Going to deploy that later today.

New Video / Blog Post: "Run Local Akka .NET Clusters with .NET Aspire" The biggest win here is that debugging / orchestrating a cluster is trivial now thanks to Aspire + Akka .Management. Links in next post.

Codex proposes adding locking, status flags, and a bunch of shared-task coordination inside a hosted service for doing skill sync in Netclaw. Me: "you know we have access to Akka .NET actors right? Just use those." * Removed 318 total LOC * Eliminated several failure classes * Made the code readable and understandable You should be using actors more. Your agents should be using them more.

We've launched official Aspire support for Akka .NET and it's live on NuGet: Akka.Aspire and Akka.Aspire .Hosting This is what it takes to launch a 3 node cluster (using Redis discovery - have another example using Azure that's about the same size) Demo on-stream today @ 12CDT

Comment I left on an /r/dotnet thread RE: "what project should I choose to get started learning Akka .NET?" TL;DR; real-time applications like live data viz, multi-player games, chat, notification systems, etc are it. They will forever change how you think about programming.

New blog: "Building a Distributed Job Scheduler with Akka .NET" Durable entity solutions such as Akka.Cluster.Sharding / Orleans are great for distributing entities, but not for distributing jobs We need something a tad different. Easy to do with Akka.Cluster + local actors

Some updates on the performance work we're doing on @AkkaDotNET v1.6. Introduced multi-plexing over a single TCP connection and we're now pushing ~2.7m msg/s over a single TCP connection. That's using "toy" messages like bare strings, byte arrays, long integers, etc.

June @AkkaDotNET Community Standup: "Agents Are Actors" featuring Netclaw. Going to get into the internals of using actors to build LLM agents and why they're the obviously best tool for the job. See you at noon Chicago Time Wednesday. Link in next post.