2 ms·
> Imagine all the wonderful things you could build if you never had to serialize data into SQL queries. This exists in sufficiently mature Actor model[0] imple
by AdieuToLogic 2y ago
> Imagine all the wonderful things you could build if you never had to serialize data into SQL queries.
This exists in sufficiently mature Actor model[0] implementations, such as Akka Event Sourcing[1], which also addresses:
> But then comes the important part: how do you recover when your process crashes? It turns out that answer is easy, periodically just take a snapshot of everything in RAM.
Intrinsically and without having to create "a new architecture for web development". There are even open source efforts which explore the RAFT protocol using actors here[2] and here[3].
0 - https://en.wikipedia.org/wiki/History_of_the_Actor_model https://en.wikipedia.org/wiki/History_of_the_Actor_model
1 - https://doc.akka.io/docs/akka/current/typed/persistence.html https://doc.akka.io/docs/akka/current/typed/persistence.html
2 - https://github.com/Michael-Dratch/RAFT_Implementation https://github.com/Michael-Dratch/RAFT_Implementation
3 - https://github.com/invkrh/akka-raft https://github.com/invkrh/akka-raft
- jeremycarter 2y agoI have built some medium sized systems using Microsoft Orleans (Virtual Actors). There was no transactional database involved, but everything was ordered and fully transactional. If you choose say Cosmos DB, MongoDB or DynamoDB as your persistence provider you can even query the persisted state. https://learn.microsoft.com/en-us/dotnet/orleans/grains/grain-persistence https://learn.microsoft.com/en-us/dotnet/orleans/grains/grai... https://learn.microsoft.com/en-us/dotnet/orleans/grains/transactions https://learn.microsoft.com/en-us/dotnet/orleans/grains/tran... https://learn.microsoft.com/en-us/dotnet/orleans/grains/event-sourcing/journaledgrain-basics https://learn.microsoft.com/en-us/dotnet/orleans/grains/even...