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.
이 주제에 관심이 있지만, 상당한 작업이 필요해 보입니다.
Google Cloud Run이 최근에 출시되었는데, "Functions as a Service"보다는 "Serverless Docker"에 더 가깝습니다.
해결해야 할 주요 문제들은 다음과 같습니다:
현재 알림을 위한 롱 폴링(long polling) 설정은 람다/클라우드 런이 타임아웃을 초과하도록 유지시켜, 비용 절감 효과를 무너뜨릴 것이라고 추정됩니다.