> A good model is an overseer program, which organizes the work to be done and aggregates the results, spawning worker programs to run the actual computations.

> A good model is an overseer program, which organizes the work to be done and aggregates the results, spawning worker programs to run the actual computations. This is not only much more robust, but it scales better, since you could distribute these programs across multiple computers later on. Splitting the application into a master process and child workers does not mean your app can magically distribute its work across machines, or gain performance from doing so. It might sometimes be easier to convert such an application to a distributed setup, as at least it contains some concept of IPC, but I wouldn't make any guarantees about that.