Interesting.. I've been trying/playing with a home-made modelling language to describe concurrent program flow and job conditions. Mostly in the context of queue-based-workers. The idea that a job can be split up in different parts and be run concurrently. Haven't cracked it yet :/
Concurrency really comes from being able to split up data in isolated chunks that have access to all their dependencies. When you think in terms of data and not tasks, things make a lot more sense.
5 comments
[ 3.2 ms ] story [ 26.3 ms ] threadhttps://github.com/LiveAsynchronousVisualizedArchitecture/la...
Concurrency really comes from being able to split up data in isolated chunks that have access to all their dependencies. When you think in terms of data and not tasks, things make a lot more sense.