Decentralized vs. Centralized Apps
Today, your app probably works something like this:
- A user installs your app or navigates to your app’s url.
- The user signs in with a username and password, or an account likely tied to a major identity provider such as Google or Apple.
- Using that provided identity as a key, your app then creates a set of entries in your databases, likely hosted by a cloud provider such as AWS, Azure, or GCP.
- As your user begins using your app, the app’s frontend will repeatedly make calls to a backend that you’ve stood up on your cloud provider to query databases and provide data to the user.
Reading this over, you’ll realize just how much of a dependency both your app and your user take on 3rd party providers. While this has been a stable model for developers for well over a decade, user identity, user data, app data, and app infrastructure are all hosted by 3rd parties. Web5 changes this by restoring control back to end users via the following flow:
- A user installs or navigates to your app’s url.
- The user signs in to your app with an account tied to their Decentralized Identifier (DID).
- Using that provided identity as a key, your app then creates a set of entries in the user’s Decentralized Web Node (DWN), a personal data store which they host and own. DWN management can be simplified for end users through the use of a wallet, making decentralized apps accessible to average end users.
- As your user begins using your app, the app’s frontend will repeatedly make calls to the user’s DWN to query and provide data to the user. If there is app data needed, the app will query the app’s infrastructure DWNs to retrieve that information.
You’ll notice that while data ownership and location radically changed between these two models, nothing changed for the end user! That means that as a developer, all you need to do to provide the benefits of a web5 application to both yourself and your end users is to simply change where your data is stored.
#web5
source:
https://developer.tbd.website/docs/web5/apps/upgrade-to-web5/#decentralized-vs-centralized-apps
mwest / Mike West
npub1h0…j32yv
2024-09-15 21:41:37
Author Public Key
npub1h09hxywtmzf2z7ff0dkktf08a8ezfawt9u39m2auv74dal8yuecssj32yvPublished at
2024-09-15 21:41:37Event JSON
{
"id": "c6becc7e13e9be60f68392d320f5c30deb0af77a1d11df6cbc59786b29660349",
"pubkey": "bbcb7311cbd892a179297b6d65a5e7e9f224f5cb2f225dabbc67aadefce4e671",
"created_at": 1726436497,
"kind": 1,
"tags": [
[
"t",
"web5"
]
],
"content": "Decentralized vs. Centralized Apps\n\nToday, your app probably works something like this:\n- A user installs your app or navigates to your app’s url.\n- The user signs in with a username and password, or an account likely tied to a major identity provider such as Google or Apple.\n- Using that provided identity as a key, your app then creates a set of entries in your databases, likely hosted by a cloud provider such as AWS, Azure, or GCP.\n- As your user begins using your app, the app’s frontend will repeatedly make calls to a backend that you’ve stood up on your cloud provider to query databases and provide data to the user.\n\nReading this over, you’ll realize just how much of a dependency both your app and your user take on 3rd party providers. While this has been a stable model for developers for well over a decade, user identity, user data, app data, and app infrastructure are all hosted by 3rd parties. Web5 changes this by restoring control back to end users via the following flow:\n- A user installs or navigates to your app’s url.\n- The user signs in to your app with an account tied to their Decentralized Identifier (DID).\n- Using that provided identity as a key, your app then creates a set of entries in the user’s Decentralized Web Node (DWN), a personal data store which they host and own. DWN management can be simplified for end users through the use of a wallet, making decentralized apps accessible to average end users.\n- As your user begins using your app, the app’s frontend will repeatedly make calls to the user’s DWN to query and provide data to the user. If there is app data needed, the app will query the app’s infrastructure DWNs to retrieve that information.\n\nYou’ll notice that while data ownership and location radically changed between these two models, nothing changed for the end user! That means that as a developer, all you need to do to provide the benefits of a web5 application to both yourself and your end users is to simply change where your data is stored.\n\n#web5\n\nsource:\nhttps://developer.tbd.website/docs/web5/apps/upgrade-to-web5/#decentralized-vs-centralized-apps",
"sig": "9d353d967257db6cfae0f028f2bd7178c88ca4bdbc9fe7a8ce496d21bed8f3c7f90d91bbdbc069d7089da80cb42d210d9a1ebeae9d535272b8dc09865e81b24f"
}