I am quite new to this buzzword “serverless”.
All that I understand is that at minimum you need one server for any deployment. In serverless you just don’t have to manage the server side of things and only focus on code development.
Since Discourse is a SaaS, I wanted to know if it’s possible for Discourse to be run as serverless application?
Like on AWS Lambda? If yes what are the benefits over running on normal instances.
performance? bandwidth? cost?
Serverless just means “running on someone else’s server”. Kind of like calling takeout kitchenless.
In this case what serverless means is that you as the application owner don’t need to think about the server - the first example that comes to mind is probably Google App Engine.
While it may be possible with a lot of effort, Discourse isn’t expected to run this way and we don’t support it.
Me interesa, pero requiere lo que podría ser mucho trabajo.
Google Cloud Run salió recientemente; en lugar de “Funciones como Servicio”, es más bien como “Docker sin servidor”.
Creo que los principales problemas que habría que resolver son:
Asumo que la configuración actual de sondeo largo para notificaciones mantendrá tus lambdas o instancias de Cloud Run activas más allá de sus tiempos de espera, arruinando todos los ahorros en la factura.