"This opinion is very specific to web server-oriented programming, and seems to boil down to this: web processing uses concurrency in many ways other than individual concurrent programs, and therefore doesn't seem to need concurrent programs. I would not disagree with that," says Reinders. "So it makes sense to me that someone working in that field would think that the revolution aspect of multi-core feels overhyped or even unreal."

"It is, nevertheless, very real and very active in other aspects of computing. It is important to understand that multi-core processors need concurrency, but that doesn't mean concurrent programs. In fact, if you can get concurrent processes and lots of them --  such as in a web server environment -- you are probably better off than having to write concurrent programs."
"I just would like to add that even in enterprise database servers that have a roughly similar architecture, multi-threading is considered important," Haghighat explains. "Initially, some of the major databases were using process-level parallelism as this was common in SMP systems. That is, each client would get a separate process on the server. Soon DB architects realized by moving from process model to thread model, there's a good amount of potential performance gain due to the sharing that happens in the memory subsystem and micro-architecture.  Care for performance justified the burden of making the database servers thread-safe. I would not be surprised to see the same thing in future on the web servers (e.g., PHP) and middleware."