Ouroboros: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
== Summary == | == Summary == | ||
Ouroboros is a prototype distributed system for packetized network communications. It | Ouroboros is a prototype distributed system for packetized network communications. It features a complete [[Ouroboros Model|redesign of the current packet networking model]] – from the programming API almost to the wire. If we had to describe Ouroboros in a single sentence, it would be | ||
Ouroboros is a micro-service architecture applied to the network itself | Ouroboros is a micro-service architecture applied to the network itself | ||
Revision as of 09:38, 28 October 2023
This page is under construction
Summary
Ouroboros is a prototype distributed system for packetized network communications. It features a complete redesign of the current packet networking model – from the programming API almost to the wire. If we had to describe Ouroboros in a single sentence, it would be
Ouroboros is a micro-service architecture applied to the network itself
While the prototype is not directly compatible with TCP/IP or POSIX sockets, it has interfaces and tools to run over Ethernet or UDP, or to create IP/Ethernet tunnels over Ouroboros by exposing tap or tun devices.
From an application perspective, an Ouroboros network is a “black box” with a simple interface. Either Ouroboros will provides a flow, a bidirectional channel that delivers data within some requested operational parameters such as delay and bandwidth and reliability and security; or it provides a broadcast channel to a set of joined programs.
From an administrative perspective, an Ouroboros network is a bunch of daemons that can be thought of as software routers (unicast) or software hubs (broadcast) that can be connected to each other; again through a simple API.