3 ms·
Yes, it reduces complexity considerably, but nearly all big systems are already built this way and are still very complex. You cannot use this approach to elimi
by pron 11y ago
Yes, it reduces complexity considerably, but nearly all big systems are already built this way and are still very complex. You cannot use this approach to eliminate complexity, i.e. make the cost linear with the system size.
Some domains where software is used to yield a tremendous economic impact are so complex that even with all complexity-management approaches at our disposal, the cost of creating them still grows super-linearly with their size.
If there are n abstract features to the system, all dependent on almost all others, you have an order of n^2 interactions. Whether you make every function its own simple communicating process, or bundle a few of them together (shifting complexity into a process) the abstract complexity of the system is still n^2.
- ta0967 11y agoYes, it reduces complexity considerably, but nearly all big systems are already built this way and are still very complex. complexity is a function of interactions. multiple processes won't do much for you if every one communicates with everybody else. If there are n abstract features to the system, all dependent on almost all others [...]. the discussion has been about using process separation as an aid in preventing accidental complexity arising from improper coupling introduced as a shortcut so this looks a little disingenuous. my response is that if you separate every function into its own simple process, a misbehaving function need not take down the whole group. on the improper-coupling-reduction front, process separation is apparently paramount to success, see eg. sendmail vs postfix.
- pron 11y agoLet me put it another way. Many of the software systems that make the biggest economic contributions have a very high essential complexity, and so their cost grows super-linearly with their size.