Having our own remote code execution engine might only work if we're already big and success. In the meantime, we can use Pesto's API to execute some code. This would mean offloading development of the remote code execution engine on the Pesto repository until everything is stable enough, or until we have some other requirements.
Other than creating a client connector to Pesto's API, we should cache every request-response of the code because it might take some time to execute them, right? The cached request calls should have some TTL.
Having our own remote code execution engine might only work if we're already big and success. In the meantime, we can use Pesto's API to execute some code. This would mean offloading development of the remote code execution engine on the Pesto repository until everything is stable enough, or until we have some other requirements.
Other than creating a client connector to Pesto's API, we should cache every request-response of the code because it might take some time to execute them, right? The cached request calls should have some TTL.