jellyfishsdk
jellyfishsdk copied to clipboard
BirthdayResearch
centralised Dex Swap indexer
What would you like to be added:
- A centralised indexer for
AccountHistoryand possibly more.
Why is this needed:
- Legacy-api
/v1/getsubgraphswapsendpoint is very slow due to getaccounthistory rpc bottlenecking.
Design
- a centralised indexing model is needed, where only 1 worker will source accounthistory data from the blocks and write the relevant data to a central, horizontally scalable database.
- The data can then be exposed via a service layer, greatly improving query performance.
- This system / approach can be leveraged for other bottlenecks if they arise.
Components
Similar to CQRS
- ETL worker to read from chain and write to db
- Managed db
- Service to expose the data
Build items
- [ ] Scaffold of the new app - #1197
- [ ] Implementation of the dex swap indexer - #1203
@eli-lim: Thanks for opening an issue, it is currently awaiting triage.
The triage/accepted label can be added by foundation members by writing /triage accepted in a comment.
Details
I am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the DeFiCh/oss-governance-bot repository.
@eli-lim: There are no 'area' labels on this issue. Adding an appropriate label will greatly expedite the process for us. You can add as many area as you see fit. If you are unsure what to do you can ignore this!
You can add area labels by leaving a /area comment.
Details
I am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the DeFiCh/oss-governance-bot repository.
A better title would be Dex Swap indexer?
Since account history involve everything, might be overkill?