Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Microservice architecture #234

Open
4 tasks
bgodlin opened this issue Dec 20, 2022 · 0 comments
Open
4 tasks

Microservice architecture #234

bgodlin opened this issue Dec 20, 2022 · 0 comments
Assignees
@bgodlin

Comments

@bgodlin
Copy link
Contributor

bgodlin commented Dec 20, 2022 •
edited
Loading

Problem

The current organization of our Subquery blockchain indexer is monolithic - all client applications send a request to a single service. Subquery is implemented in such a way that if for some reason there is a problem parsing a block, the corresponding block will not be skipped until the problem in the source code is fixed and the project is restarted => if the problem is caused by getting "fiat" values , the transaction history will also be affected.

Solution

Divide the Subquery service into different endpoints - for example, transaction history, fit values, etc.

Tasks
@bgodlin bgodlin self-assigned this Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bgodlin bgodlin

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bgodlin