Re:Why Events Are A Bad Idea For High-Concurrency Servers (2...
by Jtsummers on Friday May 02, 2014 @12:57PM
(#7686812)
Unfortunately this (in a language like C where it's not encouraged/enforced by design) requires discipline and experience. As evidenced by some colleagues, without experienced leadership on a project a group of journeyman programmers can produce some incredibly creatively broken multithreaded code. The experience part can be taught, discipline can be encouraged and developed with the right leaders/mentors. But without motivated individuals on the team (to learn this particular aspect of development) or mentors/leaders pushing/pulling them along, it's unlikely to happen until it's too late.
But, some people have to fail before they learn. Just wish they hadn't failed on such a big project.
I dispute this.
With a functional* approach to writing discrete, modular code with locking as fine-grained and minimal as possible, it's not that hard.
Lot's of threaded servers have appeared. They are, as others have said, absolutely everywhere.
*(not pure functional, just functional as an approach, i.e. writing C code in a side-effect and state-free manner as far as possible)