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

[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:

• OrbitDB
• BigChainDB
• The Graph
• Suggest more in comments

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.

[vasa-develop]

@0zAND1z Do you have any other projects/approaches in mind for dealing with dynamic data in dapps?

[0zAND1z]

Hi @vasa-develop , it is a good idea to convert this thread into a series.

Each article could spotlight how the database service offers services to dApps.

We can also add MoiBit.io into this list!