Fusion VS AsyncEx

- Even frequent exchanges like, “Hey, I’m heading to Costco, need anything?” where the follow-up is easier spoken than typed, or may require a brief brainstorming - “Oh, remember our neighbors are visiting us on Sunday?”

That’s how 8 years later (2 years ago) me and my co-founder decided to implement a new chat app.

— Technology —

To make it short, I’ll post just one point here: Actual Chat is based on Fusion (https://github.com/servicetitan/Stl.Fusion) - think MobX / computed observables, but distributed. In Actual Chat, the state it manages spans from our servers to every client app, creating an eventually consistent “state mesh”. The unified state management, where clients and servers use exactly the same abstraction to “observe” the changes happening to any bit of content, is quite a challenge from the technology standpoint. IMO it alone deserves a brief look.

P.S. Thank you for reading up to this point!

P.S. The app is created with Fusion, which is another cool thing for Blazor: https://github.com/servicetitan/Stl.Fusion

So there are different ways how you can do this, there are multiple different protocols for Unity, for example. There is also this more generic state replication framework.

There is this lib: https://github.com/servicetitan/Stl.Fusion

The library benchmarked in the article is Stl.Fusion: https://github.com/servicetitan/Stl.Fusion. I've only learned about it today, and the documentation is a bit messy, but that seems to be a really interesting project. The author describes it as a .Net library to quickly develop efficient, distributed, real-time web applications.

Disagree with every "no" here :) The answer is yes, but you need a fairly fancy "extra": https://github.com/servicetitan/Stl.Fusion/

PS: You may want to look at the other in-memory concurrency structures available. You may find something that perfectly fits the specific problem you are trying to solve. https://learn.microsoft.com/en-us/dotnet/api/system.threading?view=net-7.0, https://learn.microsoft.com/en-us/dotnet/api/system.collections.concurrent?view=net-7.0, and https://github.com/StephenCleary/AsyncEx

Async Lock.

If you haven't seen it before, there's an excellent async util library on nuget by Stephen Cleary called Nito.AsyncEx.Coordination. It contains a number of classes to help with async synchronization, giving options beyond SemaphoreSlim. It might be worth checking out.

and if you need ReaderWriterLock behavior in an async context, Stephen Cleary has an implementation

Pessimistic concurrency - you can use something like AsyncLock from Nito.AsyncEx package, to lock around each db access.

This library has class that will allow you to safely run async code in Sync-context enabled environment.

Nito.AsyncEx: