Cleary - Concurrency in C# cookbook

The next big thing in computing is making massive parallelismaccessible to mere mortals. Developers have more power available to usthan ever before, but expressing concurrency is still a challenge formany. Stephen turns his attention to this problem, helping us allbetter understand concurrency, threading, reactive programming models,parallelism, and much more in an easy-to-read but complete reference.

Scott HanselmanPrincipal Program Manager, ASP.NET and Azure Web Tools, Microsoft

The breadth of techniques covered and the cookbook format make thisthe ideal reference book for modern .NET concurrency.

Jon SkeetSenior Software Engineer at Google

Stephen Cleary has established himself as a key expert on asynchronyand parallelism in C#. This book clearly and concisely conveys themost important points and principles developers need to understand toget started and be successful with these technologies.

Stephen ToubPrincipal Architect, Microsoft

I think the animal on this cover, a common palm civet, is applicable to the subject of this book. I knew nothing about this animal until I saw the cover, so I looked it up. Common palm civets are considered pests because they defecate all over ceilings and attics and make loud noises fighting with each other at the most inopportune times. Their anal scent glands emit a nauseating secretion. They have an endangered species rating of Least Concern, which is apparently the politically correct way of saying, Kill as many of these as you want; no one will miss them. Common palm civets enjoy eating coffee cherries, and they pass the coffee beans through. Kopi luwak, one of the most expensive coffees in the world, is made from the coffee beans extracted from civet excretions. According to the Specialty Coffee Association of America, It just tastes bad.

This makes the common palm civet a perfect mascot for concurrent and multithreaded developement. To the uninitiated, concurrency and multithreading are undesirable. They make well-behaved code act up in the most horrendous ways. Race conditions and whatnot cause loud crashes (always, it seems, either in production or a demo). Some have gone so far as to declare threads are evil and avoid concurrency completely. There are a handful of developers who have developed a taste for concurrency and use it without fear; but most developers have been burned in the past by concurrency, and that experience has left a bad taste in their mouth.

However, for modern applications, concurrency is quickly becoming a requirement. Users these days expect fully responsive interfaces, and server applications are having to scale to unprecedented levels. Concurrency addresses both of these trends.

Fortunately, there are many modern libraries that make concurrency much easier! Parallel processing and asynchronous programming are no longer exclusively the domains of wizards. By raising the level of abstraction, these libraries make responsive and scalable application development a realistic goal for every developer. If you have been burned in the past when concurrency was extremely difficult, then I encourage you to give it another try with modern tools. We can probably never call concurrency easy, but it sure isnt as hard as it used to be!