New solution so called "Demux" has been released by the EOSIO blockchain.
Now, we see more and more environmental solutions around EOS blockchain to be able to adapt real Dapps and connect to the legacy technology.
In this case, it seems that the new solution connects blockchain to the legacy database of back-end infrastructure so as to reduce the RAM usage of eos blockchain.
Let's find out what this new solution means:
When building more complex DAPPs, you run into a few problems when retrieving data directly from the blockchain:
The query interface used to retrieve the indexed data is limited. Complex data requirements can mean you either have to make an excess number of queries and process the data in your DAPP, or you must store additional sorted data on the blockchain itself.
Additionally, scaling your query load means requiring more blockchain endpoint nodes, which can be expensive.
Demux draws inspiration from Facebook’s Flux Architecture pattern and Redux, creating a back-end infrastructure pattern for sourcing blockchain events in order to deterministically update queryable databases for applications built on the EOSIO blockchain.
This suggested architecture allows application developers to use traditional Mongo or Postgres SQL databases in a way that means the data stored in them is still verifiable by the blockchain. This enables the best of both worlds: the flexibility and speed of traditional databases, coupled with the trust and immutable properties of a blockchain.
Have a nice day to you all.