mesh network
This commit is contained in:
parent
985d02d420
commit
12ac75c431
19
entries/mesh_network.txt
Normal file
19
entries/mesh_network.txt
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
mesh network
|
||||||
|
|
||||||
|
A network in which there is no clear difference between clients and servers.
|
||||||
|
Instead each computer is a peer and does processing, data storage and routing
|
||||||
|
of network traffic. In the ideal mesh network data is content addressable,
|
||||||
|
such that it may be seeded by any peer, and data ownership is regulated via
|
||||||
|
cryptography.
|
||||||
|
|
||||||
|
Due to the lack of bottlenecks (servers with limited capacity), in theory
|
||||||
|
mesh networks are far more scalable than client/server, and may be the
|
||||||
|
eventual form that the internet takes. The existence of giant and highly
|
||||||
|
inefficient data centers within the current cloud computing paradigm is
|
||||||
|
really an attempt to solve the limited server capacity problem, but this
|
||||||
|
may eventually be superceded by mesh.
|
||||||
|
|
||||||
|
Existing examples of large mesh networks are freifunk and guifinet. Common
|
||||||
|
mesh protocols are batman, BMX, OLSR and Babel.
|
||||||
|
|
||||||
|
Contrast with client server.
|
Loading…
x
Reference in New Issue
Block a user