43 points | by ahelwer 3 days ago
5 comments
As I understand it, the parallelism is about task execution and concurrency is about task structure. Or, as Rob Pike said:
"Concurrency is about dealing with lots of things at once. Parallelism is about doing lots of things at once."
He said that in his *Concurrency is not Parallelism" talk.
You can't unit test your way out, but if you care about the code's correctness, today there's a way.
Best examples are SQLite and Jepsen test suites for dbms engines.
https://jepsen.io/
Then comes the parallel debugging.
Pretty soon it's 15 years later, different person, yahoo-wee bro having long moved on.
As I understand it, the parallelism is about task execution and concurrency is about task structure. Or, as Rob Pike said:
"Concurrency is about dealing with lots of things at once. Parallelism is about doing lots of things at once."
He said that in his *Concurrency is not Parallelism" talk.
You can't unit test your way out, but if you care about the code's correctness, today there's a way.
Best examples are SQLite and Jepsen test suites for dbms engines.
https://jepsen.io/
Then comes the parallel debugging.
Pretty soon it's 15 years later, different person, yahoo-wee bro having long moved on.