Network engineering continued

 This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html 

The total cost of ownership encompasses cost for operations and is usually not reflected on new instances of the networking services. It is used with products that have been used for a while and are becoming a liability.

A higher layer that manages and understands abstractions, provides namespace and data operation ordering and protocol handling is present in many networking services. 

A lower layer comprising of distribution and replication of data without actually requiring any knowledge of abstractions or protocols maintained by the higher layer is similarly present in many networking products.

Similarly, the combination of the  layers described above is almost always separated from the front-end layer interpreting and servicing the user requests.

Working with streams is slightly different from fixed sized data. It is an ordered set of references to segments. All the extents are generally immutable.

If a shared resource can be represented as a pie, there are two ways to enhance the usage: First, make the pie bigger and the allocate the same fractions in the increment. Second, dynamically modify the fractions so that at least some of the resource usages can be guaranteed some resource.