Universal Scalability Law: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 8: Line 8:
* [[Software Architecture#Subjects|Software Architecture]]
* [[Software Architecture#Subjects|Software Architecture]]
* [[Reactive Programming]]
* [[Reactive Programming]]
* [[Amdahl's Law]]


=Overview=
=Overview=


Pushing utilization beyond a certain point will yield diminishing or even negative returns. This observation was formalized by Neil J. Guther as Universal Scalability Law (USL).
Pushing utilization beyond a certain point will yield diminishing or even negative returns. This observation was formalized by Neil J. Guther as Universal Scalability Law (USL).
USL introduces the cost of communication - coherency, or the cost of keeping data in sync - as a variable in the equation.

Latest revision as of 04:16, 31 December 2023

External

Internal

Overview

Pushing utilization beyond a certain point will yield diminishing or even negative returns. This observation was formalized by Neil J. Guther as Universal Scalability Law (USL).

USL introduces the cost of communication - coherency, or the cost of keeping data in sync - as a variable in the equation.