If you use https://t.co/916SOQ1bBk, upgrade to 1.5.71 now.
It fixes two snapshot-store bugs that could use the wrong sequence number during recovery and potentially cause missing data.
Release notes: https://t.co/cv7Nrmg6f4
New live https://t.co/bwaZZvEppl training dates are available for Q4.
Join instructor-led sessions on Akka.Streams, Akka.Cluster, and end-to-end application design.
See the full calendar and reserve your spot:
https://t.co/AizX64dRs9
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.
Akka .NET 1.5.71 is out.
This maintenance release includes targeted fixes for Cluster Sharding recovery, remoting, TestKit / multi-node testing, and ClusterClientDiscovery.
If you’re running any of those components, review the notes and plan the upgrade:
https://t.co/7QPuu30Zdq
Imagine you have to schedule a big burst of data-intensive jobs in short order. How do you achieve this with minimal fuss? In this post we show how to use Akka .NET to achieve it.
https://t.co/WzoIIow4xh via Aaron Stannard @Aaronontheweb
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.
I'll be available for remote/hybrid contracts starting in the next month or so. Engineering roles leveraging functional programming (F#), AkkaDotNet preferred. Reach me here: https://t.co/2AbuLfdGYv
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
@Aaronontheweb That looks exactly what I did while I worked with AkkaNET.
Working with sensors, IOT, and different types of manufacturers is really time consuming. Creating an simulador for each one of them is also a Good blueprint on how to implement such integrations.
Tomorrow at 12pm Chicago Time - join us our on YouTube channel for our July @AkkaDotNET Community Standup, during which we'll discuss the amazing progress we're making on v1.6 and how Akka.Remote is _at least_ 2.1x faster for benchmarked workloads.
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.