End-to-end principle: Difference between revisions
Jump to navigation
Jump to search
Amwelladmin (talk | contribs) (Created page with "The end-to-end principle is a design framework for distributed systems. In networks designed according to this principle, application-specific features reside in the communica...") |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
The end-to-end principle is a design framework for distributed systems. | The end-to-end principle is a design framework for distributed systems. It counsels that the network should be kept as simple as possible and the intelligence required in a network be kept at the ends of the network - the entry points to it, in other words, as far as possible<ref>Lawrence Lessig, ''Code 2.0'',126.</ref>. On a computer network, that would mean "application-specific" complexity would be in the communicating end nodes of the network, rather than in intermediary gateways and routers, that comprise establish the network. | ||
In the case of the internet, the basic layer of the network is a TCP/IP protocol that sends packets of very basic data across the network. | |||
Consequences of this design philosophy: | |||
*You can innovate on the network without bothering the network "owner". This avoids "strategic" behaviour by the network owner (such as interfering to stifle the innovation). | |||
Revision as of 15:49, 6 May 2017
The end-to-end principle is a design framework for distributed systems. It counsels that the network should be kept as simple as possible and the intelligence required in a network be kept at the ends of the network - the entry points to it, in other words, as far as possible[1]. On a computer network, that would mean "application-specific" complexity would be in the communicating end nodes of the network, rather than in intermediary gateways and routers, that comprise establish the network.
In the case of the internet, the basic layer of the network is a TCP/IP protocol that sends packets of very basic data across the network.
Consequences of this design philosophy:
- You can innovate on the network without bothering the network "owner". This avoids "strategic" behaviour by the network owner (such as interfering to stifle the innovation).
- ↑ Lawrence Lessig, Code 2.0,126.