These are chat archives for akkadotnet/akka.net
PersisentReadViewcan then publish those messages to any other actors who need it
Say I have a cluster running and I'm using EventsourcedActors. How do instances on other nodes keep up to date?
@trbngr When it comes to
PersistentActor, you can't use more than one per it's persistence Id in akka cluster scope. They have to be singletons
PipeTomethod - which is preferred way of dealing with async APIs in Akka. This could be potentially improved, but would require major rewrites of akka internals and will break existing API
When it comes to PersistentActor, you can't use more than one per it's persistence Id in akka cluster scope. They have to be singletons
What about synchronizing the states of the views? Storages like EventStore has some mechanims for subscribing to event streams.
something which might get improved by akka or are you bound by the TPL impl of Microsoft?
We are bound by the use of an ambient context backed by
ThreadStatic field. This sort of things just won't work well with async/await, that's why a custom
TaskScheduler is used. And that
TaskScheduler don't execute stuff on threadpool like default does, it messes up with akka's internals to pause actor's mailbox and executes async callbacks on akka's dispatcher. That's why you shouldn't use it for anything other than I/O operations that absolutely have to be completed before processing the next message.
Updatemessage back to them. I know that this is bad, and when akka streams will be ready to be used, we'll change persistent views to use streaming, but until then we have to stick with that.
AsyncWriteJournalyou may use
akka.persistence.publish-plugin-commands- if you set this on, then journal will emit all of it's messages on the akka event stream
Akka.Cluster.Shardingwill come out we'll have to do them manually
ShardRegionclass porting, I think that after it's complete, we have 1 more event to introduce in
ClusterShuttingDownevent I guess)
I need some simple (eg. bubblesort), short (1-2 pages of code) and easy to comprehand example where Akka shines and 'classic' methods are being ugly