I feel the Autoscale function is a very interesting new way of having Always On Repls without paying as much as with Fixed Deployment server. But I’m not sure and I would be happy to have answers to some questions :
In a Python Flask app, the web server keeps waiting for a connection to render the templates. That means the server is always on but doing almost nothing. Is the Autoscale server always up and using few compute units or does it close and restart when not used ?
If I have a server that does almost nothing, just serving few requests every month, is it more expensive to create a Autoscale server with 2 CPU and 8GB RAM and let it do almost nothing or just take the smallest one ? I mean, with the same usage, is it less expensive to have a small server or not ?
My main issue about Deployment is that I can’t access the filesystem to check logs or file creations. And if the deployment crash or I need to deploy again, I lose everything. Is there a possibility to have a deployed Repl share the filesystem or use files on another Repl ? Having presistent file system with deployed Repls would be great
Do you plan to remove Always On feature and ask people to use Deployment instead ?
@IroncladDev I hope you’ll be able to help me