Like jars of honey, a database has a capacity, and like the jar example you cannot overfill the database or things get messy.
Database capacity can be thought of in many different ways.
If a database has a capacity problem like the ones above, there are various solutions. Examples 1 and 2 above may require the most drastic remedial action. The latter two examples may be more simply solved.
1. Smaller faster, cheaper, lighter computers for the desktop. They will be no larger than a DVD drive. They will be silent, and run free software, and much of this will be web based. They will use solid state disks, and large quantities of cheap memory.2. More powerful mobile phones will largely replace traditional PCs. The screens of mobiles will occupy as much of the phone as physicallly possible. "Soft buttons will have largely replaced mechanical buttons in top of the range phones.
3. Sophisticated screen display technology will be available that will allow us to use bigger computer monitors in smaller less likely workplaces.
4. Micro-factories: places of work no bigger than a loft
extension, where budding entrepreneurs labour in their free time
"printing" products with 3D printers and selling their wares
by the internet.