I personally love serverless for its low cost and ability to handle potential burst. The framework would try to adapt serverless but it is not a focus (I will change the README later).
> How cron jobs work in such a environment? They spin up another function?
While deploying in the long running machine is the best practice for now, I usually deploy the worker with serverless functions + a cron trigger (5 sec interval). I plan to develop a dedicated trigger to invoke worker when there is an event waiting for handling.
Overall, the framework will adapt the serverless environment, but not focusing on serverless.
> How do you deploy those functions?
In production, I deploy the server in serverless environment like AWS Lambda, with worker-mode turned off (in that case, server will not pull tasks from the queue), then I deploy the woker in long running machines like AWS ECS.
I personally love serverless for its low cost and ability to handle potential burst. The framework would try to adapt serverless but it is not a focus (I will change the README later).
> How cron jobs work in such a environment? They spin up another function?
While deploying in the long running machine is the best practice for now, I usually deploy the worker with serverless functions + a cron trigger (5 sec interval). I plan to develop a dedicated trigger to invoke worker when there is an event waiting for handling. Overall, the framework will adapt the serverless environment, but not focusing on serverless.
> How do you deploy those functions?
In production, I deploy the server in serverless environment like AWS Lambda, with worker-mode turned off (in that case, server will not pull tasks from the queue), then I deploy the woker in long running machines like AWS ECS.