| Introduction | Setup | Peer | Server | Centralised | DHT | Presentation | Architecture-Basic | Architecture-Operation |
Centralised P2P is a type of P2P that involves a central entity or server.
So Centralised P2P involves a server...
In what way is that different from a non-P2P setup?
Well this is what a client-server model would look like:
When we use client-server, all of our messages are communicated to the server (who then in turn, forwards that messages to it's intended recipient).
In Centralised P2P, that message is deliverered directly. And our server doesn't even have to know about it.
So how exactly does Centralised P2P help us? What problems does it solve and what problems doesn't it?
Well first of all, it reduces server load. Our server's role is easy. All it has to do is index the details (IP address and port) of each peer in the network.
However, the obvious flaw of any setup that involves a server exists in Centralised P2P.
The entire system is dependent on the server (central entity) functioning. If the server dies or loses connection, our system doesn't work anymore.