2 ms·
The current mainstream distinction seems to be: Parallelism - actually running (or intended to run) in parallel. A lot of computational work is like this. Con
by Jtsummers 5y ago
The current mainstream distinction seems to be:
Parallelism - actually running (or intended to run) in parallel. A lot of computational work is like this.
Concurrency - may run in parallel, but is about design as much, if not more, than execution.
Concurrency is a way (in the current mainstream sense) to decompose a program into multiple "processes" (generic sense) much like we decompose programs into functions, procedures, and objects in other languages. I think it was Rob Pike's talk "Concurrency is not parallelism" which pushed this distinction further into the mainstream.
https://go.dev/blog/waza-talk https://go.dev/blog/waza-talk - Concurrency is not parallelsim, Rob Pike
Go, Erlang (later Elixir), and Clojure in particular seem to have pushed the idea of using concurrency (above sense) in the design of programs into the mainstream. Specifically bringing concurrency into "the small". Concurrency is an innate quality of networked programs, but within a program people often write sequential (non-concurrent) code and only add concurrency elements to access parallelism for performance (vice adding them because they clarify the code or its design). But many problems are neatly decomposed into well-performing concurrent designs that may get a performance boost if you have multiple cores available, but it isn't (strictly) the point of using concurrency.