This is a continuation of the article at http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html
Protection against loss – Data when stagnant may get corrupted. In order to make sure the data does not change; we need to keep additional information. This is called erasure coding and with additional information about the data, we can not only validate the existing data, but we may also even be able to recreate the original data by tolerating certain loss. How we store the data and the erasure code, also determines the level of redundancy we can use. If the data is in transit, it can be made immutable and uninterpretable with encryption
Hot warm cold – Data differs in treatment based on the access. Hot data is one that is actively read and written. Warm and cold indicate progressive inactivity over the data. Each of these labels allows different leeway with the treatment of the data and the cost of network flow.
The organizational unit of data – Networking is always in layers due to the separation of concerns in each layer and its communication with a peer at the same level across a hybrid network.
Seal your packet – Every packet has a header and a payload start and length. Even if the data is chunked, the packet has to be well-formed so that any tool or application can validate the packet for its representation.
Versions and policy – As with most libraries, packet headers can be versioned and versions can be managed with policies. Headers may be static but policies can be dynamic. When a software-defined network is viewed as revisions, users can go back in time and track revisions.
No comments:
Post a Comment