This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html
In-memory server: If the networking server is stateless, it can run entirely in-memory require no state persistence. A server that runs entirely in-memory with little or no disk access can improve performance by orders of magnitude.
Distributed ledger: this is gaining popularity where there is no central ledger and no requirement for central ownership for verification of grants and revocations. It mitigates tampering. It is great storage for storing and processing network data and works for products that do not belong to an organization or cloud.
Footprint: The code for a networking server can run on any device. Java, for example, runs on billions of devices and a networking server written in Java can run even on pocket devices. If the storage is flash and the entire storage server runs only on flash, it makes a great candidate for usability.
Editions: Just like the code for networking service can be made suitable for different devices, it can ship as different editions. One way to determine the different kinds of editions is to base it on where the customers demand it. Although there are many perspectives in these decisions, the ultimate service of the product is for the customer.
Standalone mode: Most networking products offer capabilities in a standalone mode. This makes it easy to try out the product without dependencies. One Box deployments also work in this manner. When we remove the dependency on the hardware, we enable the product to be easier to study and try out the features.
No comments:
Post a Comment