Cleanup - there are a lot of old constructs and that can be removed from Akka.NET.Ĭontributing to the v1.5 effort is somewhat different than our normal maintenance contributions to Akka.NET,in the following ways:.Leverage Microsoft.Extensions more closely - consume from HOCON, allow interplay, and more.Make CQRS a priority in Akka.Persistence - tags are an especially weak area for Akka.Persistence right now, given that they require table scans.NET 6+ primitives for improved performance - thread execution, zero-allocation System.Memory data structures, and more. Improved Akka.Cluster formation experience - in layman's terms this means releasing Akka.Management out of beta and incorporating it into the Akka.Cluster literature and code samples.Improved default serialization options - Newtonsoft.Json sucks.Improved Akka.Remote + Cluster.Sharding performance - we want to go from ~350,000 msg/s to 1m+ msg/s in our RemotePingPong benchmark by changing the design of Akka.Remote's actors and optionally, replacing our transports.Better documentation and examples - after simplifying the Akka.NET APIs around configuration and startup, modernizing all samples and deployment guidance is the biggest issue affecting end-users.While not every technical detail is finalized yet, we do want to share the goals and some of the specific plans of what's included in this next minor version release of Akka.NET! Goalsīased on feedback from Akka.NET users, here are the top priorities: Beginning with our March 9th, 2022 Akka.NET Community Standup we've shared our plans for the roadmap of Akka.NET v1.5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |