Is there a paradigm that gives you a different mindset or have a different take to writing multithreaded applications?
Perhaps something that feels vastly different, like procedural programming to functional programming.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there a paradigm that gives you a different mindset or have a different take to writing multithreaded applications?
Perhaps something that feels vastly different, like procedural programming to functional programming.
Concurrency has many different models for different problems. The Wikipedia page for concurrency lists a few models and there’s also a page for concurrency patterns which has some good starting point for different kinds of ways to approach concurrency.
The approach you take is very dependent on the problem at hand. Different models solve various different issues that can arise in concurrent applications, and some build on others.
In class I was taught that concurrency uses mutual exclusion and synchronization together to solve concurrency issues. Some solutions only require one, but with both you should be able to solve any concurrency issue.
For a vastly different concept you could look at immutability and concurrency. If all data is immutable then the conventional approaches to concurrency aren’t even required. This article explores that topic.