Better repo actor system #4

New issue

Closed

opened 2024-06-19 23:47:21 +02:00 by Jef Roosens · 0 comments

Jef Roosens commented

2024-06-19 23:47:21 +02:00

Owner

On startup, start N actors with their own threads (outside of Tokio, using std:🧵:spawn) that perform repository tasks such as syncing etc.
these all listen to the same mspc channel, with the global state containing a repository handle that uses this channel to communicate
Each of these actors get a handle to the tokio runtime so they can use block_on to execute async functions while remaining sync themselves (e.g. database operations)
the important part here is that we can bring all io into a few threads without having to spam spawn_blocking

based on https://tokio.rs/tokio/topics/bridging#a-synchronous-interface-to-mini-redis

* On startup, start N actors with their own threads (outside of Tokio, using std::thread::spawn) that perform repository tasks such as syncing etc. * these all listen to the same mspc channel, with the global state containing a repository handle that uses this channel to communicate * Each of these actors get a handle to the tokio runtime so they can use `block_on` to execute async functions while remaining sync themselves (e.g. database operations) * the important part here is that we can bring all io into a few threads without having to spam `spawn_blocking` based on https://tokio.rs/tokio/topics/bridging#a-synchronous-interface-to-mini-redis