I did think about this. It is an awful lot of processes for just a map.
There maybe a tiny concurrency benefit when ‘casting’ the action down the tree.(if it’s big enough)..but probably doesn’t outweigh the msg overhead. Also have not really tried, but failure may also be isolated…an action that crashes a reducer might some how be recoverable at only that level and below on the state tree…
Am considering @sasajuric ‘Parent’ to flatten that tree…each aggragate reducer is a genserver and a dynamic supervisor… So could remove atleast 3 processes from that tree I believe.
If my thoughts are wrong, would definately consider a simpler design…
Every stateful LiveView is a process, so if they can do it… 
Thanks for checking it out!
