Generally a server may be challenged beyond its capabilities. Then a single server may cause a bottleneck or constraints problem. However, servers may be cloned and networked for capacity and performance. Limitations include network load, network address volume, and transaction recovery time.
Client/server architecture compete with cloud computing. Factors affecting a design decision could be:
As soon as the total number of simultaneous client requests made to a server increases, the server can become overloaded. Contrast that to a P2P network, where its aggregated bandwidth actually increases as nodes are added, since the P2P network's overall bandwidth can be roughly computed as the sum of the bandwidths of every node in that network. However, this simple model ends with the bandwidth of the network: Then congestion comes on the network and not with the peers.
Any single entity paradigm lacks the robustness of a redundant configuration. Under client–server, should a critical server fail, clients’ requests cannot be fulfilled by this failed entity, but may be taken by another parallel server which has access to the same data as the failed entity. In P2P networks, resources are usually distributed among many nodes which generate as many locations to fail. If dynamic re-routing is established, even if one or more nodes depart and abandon a downloading file, for example, the remaining nodes should still have the data needed to complete the download.
Mainframe networks use dumb terminals. All processing is completed on few central computers. This is a method of running a network with different limitations compared to fully fashioned clients.
No comments:
Post a Comment