You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would love to see some alternative transport layers for Akka.Remote.
Lately there have been a lot of questions regarding different network aspects, security, throughput etc.
And I do think it would be beneficial the more integrations we have.
For example,
X-Sockets.NET
Libuv (NodeJS socket layer)
Libuv is known for its high performance, it would be very interesting to see how that would work with our stack even if the lib itself is native.
X-Sockets.NET is pure .NET but comes with a lot of options and integrations.
Even if such effort turns out to not be used by anyone, it still shows the community what can be done with Akka.NET, and there are always some users that have firm opinions on what to use.
The more options the better imo, just to grow the ecosystem around us.
(And I dont mean that the core team should bother with this, but it could be a nice exercise for the community)
The text was updated successfully, but these errors were encountered:
Copy of akkadotnet/akka.net#1017
I would love to see some alternative transport layers for Akka.Remote.
Lately there have been a lot of questions regarding different network aspects, security, throughput etc.
And I do think it would be beneficial the more integrations we have.
For example,
Libuv is known for its high performance, it would be very interesting to see how that would work with our stack even if the lib itself is native.
X-Sockets.NET is pure .NET but comes with a lot of options and integrations.
Even if such effort turns out to not be used by anyone, it still shows the community what can be done with Akka.NET, and there are always some users that have firm opinions on what to use.
The more options the better imo, just to grow the ecosystem around us.
(And I dont mean that the core team should bother with this, but it could be a nice exercise for the community)
The text was updated successfully, but these errors were encountered: