🚀 go-pugleaf

An anology (thought probably not original with me, this manifestation is)

A mainframe system is like a railroad.  If you have to move lots of freight
(data) consistently from one station to another station in a very reliable
manner, then a "railroad" is the way to go.  Trucks could do the job, but
trucks are expensive progressively more expensive just to do the same thing
over and over again.  Railroads have a very high initial expenditure and
startup cost, but for day in and day out service, they are useful. 
However, they are not flexible.  If you add another station to the mix,
then you have to plan extensively and construction  costs are very high. 
This system is not cost effective for small loads, unless there are a
tremendous number of small loads, all going the same way.  While much fewer
personnel are required to run the system, they are specialized personnel,
more costly and with a much longer apprenticeship time.

However, if you job is to move smaller freight, all over the place, then a
truck fleet is better.  You can own one truck or thousands.  They are
extremely versitile in their cargo carrying ability and come in lots of
different styles and shapes.  The total size of the cargo is the limiting
factor.  Fexibility is much greater, also.  A truck can be moved on a
moments notice.  Personnel training time is significantly reduced,
especially for the drivers.  Also the drivers can respond to local
conditions and on their own initiative, redirect the process.  Trucking
fleets can be expanded to meet changing needs by adding units obtainabile
from any locality.  Overally costs are probably similiar for the two
systems providing total cargo capacity is the same.

Many larger businesses are moving into a combo system utilizing both, but
significantly increasing the complexity of their overall system by trying
to make both work at the same time.

I'm sure that given more time, this anology could be polished better and
expanded.
  
What do you all think......