https://fsharpforfunandprofit.com/categories/concurrency/ Recent content in Concurrency on F# for Fun and Profit Hugo -- gohugo.io en-us Thu, 26 Apr 2012 00:00:00 +0000 https://fsharpforfunandprofit.com/posts/concurrency-reactive/ Thu, 26 Apr 2012 00:00:00 +0000 https://fsharpforfunandprofit.com/posts/concurrency-reactive/ Events are everywhere. Almost every program has to handle events, whether it be button clicks in the user interface, listening to sockets in a server, or even a system shutdown notification. And events are the basis of one of the most common OO design patterns: the “Observer” pattern. But as we know, event handling, like concurrency in general, can be tricky to implement. Simple event logic is straightforward, but what about logic like “do something if two events happen in a row but do something different if only one event happens” or “do something if two events happen at roughly the same time”. https://fsharpforfunandprofit.com/posts/concurrency-actor-model/ Wed, 25 Apr 2012 00:00:00 +0000 https://fsharpforfunandprofit.com/posts/concurrency-actor-model/ In this post, we’ll look at the message-based (or actor-based) approach to concurrency. In this approach, when one task wants to communicate with another, it sends it a message, rather than contacting it directly. The messages are put on a queue, and the receiving task (known as an “actor” or “agent”) pulls the messages off the queue one at a time to process them. This message-based approach has been applied to many situations, from low-level network sockets (built on TCP/IP) to enterprise wide application integration systems (for example RabbitMQ or IBM WebSphere MQ). https://fsharpforfunandprofit.com/posts/concurrency-async-and-parallel/ Tue, 24 Apr 2012 00:00:00 +0000 https://fsharpforfunandprofit.com/posts/concurrency-async-and-parallel/ In this post we’ll have a look at a few ways to write asynchronous code in F#, and a very brief example of parallelism as well. Traditional asynchronous programming As noted in the previous post, F# can directly use all the usual .NET suspects, such as Thread AutoResetEvent, BackgroundWorker and IAsyncResult. Let’s see a simple example where we wait for a timer event to go off: https://fsharpforfunandprofit.com/posts/concurrency-intro/ Mon, 23 Apr 2012 00:00:00 +0000 https://fsharpforfunandprofit.com/posts/concurrency-intro/ We hear a lot about concurrency nowadays, how important it is, and how it is “the next major revolution in how we write software”. So what do we actually mean by “concurrency” and how can F# help? The simplest definition of concurrency is just “several things happening at once, and maybe interacting with each other”. It seems a trivial definition, but the key point is that most computer programs (and languages) are designed to work serially, on one thing at a time, and are not well-equipped to handle concurrency.