Decentralized web — network architecture, participants and evolution

1. Current participants

This article gives a high level overview of the network architecture of the decentralized web / dWeb project — in its current state and how it is evolving.

2. Current connection cases

The following cases are assuming that both usr1 and 2 are online and internet connection is on.

user1(O&I) and user2 (OO)
user1(O&I) and user2 (O&I)
user1(OO) -> <- user2 (OO)

3. Assisting outward only users — introducing a new participant

To assist in the most common case of users being 1 directional (OO) we are introducing a new 2 directional (O&I) participant — a bridge.

user1(OO) , bridge1(O&I) and user2 (OO)

4. Decentralized Network architecture, comparing it with blockchain networks

In summary the evolved Decentralized Network architecture has a mixture of:
- OO and O&I participants
- temporary and permanent participants
- participants with fixed and changing location
- users (consumers) and bridges (network support nodes)

5. Implementation of bridge nodes

Implementation of bridge nodes is under current development. We have 2 current choices:

raspberry pi3
  • Pi bridge — on raspberry pi3 hardware, running minimal Linux OS. It does not only forwarding of data, but can potentially store messages received, run smart contracts, and host personal web sites
android tablet & phone
  • Android bridge — on android phone, or tablet; usually older version/release, just sitting unused at home

References

Decentralized web — User’s guide / tutorial

Connect with us:

on LinkedIn , by email , on Twitter ,

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
paul arssov

paul arssov

Creating the decentralized web — https://decentralizeweb.org, building a decentralized communication platform