Skip to content

RFC: What are different methods to store dynamic data in a dapp? #51

@vasa-develop

Description

@vasa-develop

What new topic/thread/tutorial are you proposing? Please describe.
We know that dealing with "changing data" is a thing greatly discussed in the Web 3.0 community. The thing here is that immutable stores(Blockchains, IPFS, etc.) are good for static data, i.e. data that is not supposed to change.

But a big part of a dapp consists of dealing with your dynamic data(users and their related properties, assets, etc.). There are a few approaches that we use today to mitigate this:

The purpose of this post(maybe series) is to study different scenarios in which we need to manage(store, fetch, edit) dynamic data of our dapp, and see which approaches work best for different scenarios.

Metadata

Metadata

Labels

new-rfcTo identify incoming RFCs (for review purposes)

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions