I agree, I have settled on a similar principle for the small systems I build: Reduce distributed state and message passing as much as possible, use only one pro

I agree, I have settled on a similar principle for the small systems I build: Reduce distributed state and message passing as much as possible, use only one process if possible. I think I have settled on a typed language using async and writing state to disk with SQLite. The async functions give me much more context than messaging (Golang, Erlang, GRPC etc) as they preserve the function call stack, SQLite is just the "sync" part of a SQL engine so no message passing there, and types give me machine checkable interfaces. It's going ok.