This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html
P2P can be structured or unstructured.
Messages are helpful to enforce consistency as nodes come up or go down. For example, a gossip protocol may be used for this purpose and it involves propagating updates via message exchanges.
Message exchanges can include state or operation transfers. Both involve the use of vector clocks.
A utility token issued for authorization need not be opaque. It can be made up of three parts – one which represents the user, another which represents the provider, and an irrefutable part that is like a stamp of authority. The section from the provider may also include scope for the resources authorized.
The attestation mechanism itself might vary. This might include, for example, Merkle tree where each node of the tree represents an element of Personally-Identifiable-Information (PII) along with the hash and the hash of the hashes of the child nodes. The root hash then becomes the fingerprint of the data being attested.
An immutable record which has its integrity checked and agreed upon on an ongoing basis provides a venerable source of truth.
A rewarding service increases appeal and usage by customers. This is what makes Blockchain popular.
Many clusters are used as a failover cluster and not as a performance or scalable cluster. This is primarily because a server is designed for scale-up versus scale-out. This is an emphasis on the judicious choice of technology for design.
Some servers use shared storage and do not go offline. Most products have embraced Network Access Storage. Similar considerations are true when a database server is hosted on a container and the database is on a shared volume
The clustering does not save space or efforts for backup or maintenance. And it does not scale out the reads for the database. Moreover, it does not give a 100% uptime for a database.
#codingexercise: https://ideone.com/DBjnkH
No comments:
Post a Comment