onto an AWS lambda. It might get a bit pricey (or not, depending on how long we set the timeout), but it is really the only way we get proper scaling with lots of users.
For now, we should just migrate that call to an AWS Lambda, but eventually, we should put a caching system in between so we don't waste as much time. Maybe the caching also goes into the lambda?
We should put the call to cvc5 that occurs here:
https://github.com/Barnard-PL-Labs/SequencerLiveCoding/blob/e63429a562506f5caf73ad0c1b98e37e4c0b0bfe/serverSide/cvc4.js#L71
onto an AWS lambda. It might get a bit pricey (or not, depending on how long we set the timeout), but it is really the only way we get proper scaling with lots of users.
For now, we should just migrate that call to an AWS Lambda, but eventually, we should put a caching system in between so we don't waste as much time. Maybe the caching also goes into the lambda?