Basic transaction prover service has been implemented in #881. The current implementation handles only one request at a time (if another requests arrives, it rejects it with a "busy" error). We need to extend the current implementation to allow handling of multiple requests.
One approach to this is to introduce some kind of "coordinator" service which would accept incoming transaction requests and dispatch them to a pool of prover servers. A few things to consider:
When a prover spins up, it would need to notify the coordinator that it is available.
The coordinate would need to be able to perform liveness checks on a prover server (e.g., "ping" or something like that).
The coordinator would need to either queue or reject requests if no provers are currently available to handle them.
Basic transaction prover service has been implemented in #881. The current implementation handles only one request at a time (if another requests arrives, it rejects it with a "busy" error). We need to extend the current implementation to allow handling of multiple requests.
One approach to this is to introduce some kind of "coordinator" service which would accept incoming transaction requests and dispatch them to a pool of prover servers. A few things to consider: