This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html
Reconfiguration: Most networking products are subject to some pools of available resources managed by some policies that can change from time to time. Whenever the network resources are changed, they must be done in one operation so that the network presents a consistent view for all usages going forward. Such a network-wide reconfiguration is supported across network servers.
Auto-tuning: This is the feedback loop cycle with which network server/appliance/product can be made to perform better because the dynamic parameters are adjusted to values that better suit the workload.
Acceptance: This is the user-defined level of service-level agreement for the APIs to the storage server so that they maintain satisfactory performance with the advantage that the clients can now communicate with a pre-existing contract.
Address: This defines how network service is discovered by clients. For example, if there were a network local address or a bridged mode bidirectional reachability, this would define how the host / service would be reached. If there were a network share on the host, this would define who can access it. Enabling DMZ is a way to prevent reachability in unwanted cases. Since it can be virtual some network products may provide a gateway to those addresses.
Binding: A binding protocol defines the transport protocol, encoding, and security requirements before the data transfer can be initiated. Although network products may default to tcp binding for internal networks and http binding for external by default, this could determine stateful or stateless connections.
No comments:
Post a Comment