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.

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

Archival support without requiring a separate gw instance #286

Open
Yawning opened this issue Jun 8, 2022 · 0 comments
Open

Archival support without requiring a separate gw instance #286

Yawning opened this issue Jun 8, 2022 · 0 comments
Labels
enhancement New feature or request p:2 Priority: desired feature performance

Comments

@Yawning
Copy link
Contributor

Yawning commented Jun 8, 2022

nb: Filing this here, though this probably needs changes in https://github.com/oasisprotocol/oasis-sdk

The archive node support as implemented in #281 is sub-optimal in that it uses a dedicated web3 gw instance to handle queries that hit up the archival oasis-node instance. This is because oasis-node's grpc interface is not guaranteed to be stable and in fact has changed in a binary incompatible way.

As it is essentially impossible to import multiple versions of go packages in a useful manner (No, replace in go.mod does not work), the decision was made to use an archival web3 gateway instance that the non-archival web3 gateway instance will query to service 5 calls.

While there is (untested) support for having web3 gateway instances share the backing database, in an ideal world, a single web3 gateway instance will be able to handle both current and archival queries.

@Yawning Yawning added enhancement New feature or request p:2 Priority: desired feature performance labels Jun 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request p:2 Priority: desired feature performance
Projects
None yet
Development

No branches or pull requests

1 participant