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

Batching multi-chain Pact service endpoints #1314

Open
sirlensalot opened this issue Nov 24, 2021 · 1 comment
Open

Batching multi-chain Pact service endpoints #1314

sirlensalot opened this issue Nov 24, 2021 · 1 comment

Comments

@sirlensalot
Copy link
Contributor

Offer a new set of endpoints for the pact API that are "chain independent" and essentially dispatch to the appropriate apis, since txs self-identify for chains

  • send can be unchanged as it's already batch
  • local changes so maybe has a different name (locals?)
  • poll is batching but might require chain IDs, if so a new name (polls?)
  • listen is not indicated for this feature, and offering some kind of join is probably not merited.
@sirlensalot sirlensalot changed the title Batching multi-chain endpoints Batching multi-chain Pact service endpoints Nov 24, 2021
@larskuhtz
Copy link
Contributor

Internally, chainweb-node is shared by chain. Each chain has its own pact api. Adding chain independent APIs would change that paradigm and make future physical sharding more difficult.

Even if we add a global ingress in front of the shared pact services, routing would become more difficult, because the proxy would need to parse the request bodies in order to find out to which service to forward to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants