# Serverless Discourse

**URL:** <https://meta.discourse.org/t/serverless-discourse/103726>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [December 7, 2018, 7:37pm UTC](https://meta.discourse.org/t/serverless-discourse/103726 "2018-12-07T19:37:04Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![InstanceOfMichael](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/instanceofmichael/32/162181_2.png) [@InstanceOfMichael](https://meta.discourse.org/u/InstanceOfMichael)\
**Post date:** [November 25, 2019, 10:45pm UTC](https://meta.discourse.org/t/serverless-discourse/103726/3 "2019-11-25T22:45:48Z")

</div>

I’m interested in this, but it needs what could be a lot of work.

Google Cloud Run came out recently, instead of “Functions as a Service” it’s more like “Serverless Docker”.

I think the big issues that would need to be resolved are:

- uploadables need to go to S3
- MessageBus needs a dedicated pusher (mercure, [pusher.io](http://pusher.io), ably) or to be disabled.

I’m assuming the current long polling setup for notifications is going keep your lambdas/cloud runs running past their timeouts, destroying all your bill savings.

---

_[View the full topic](https://meta.discourse.org/t/serverless-discourse/103726)._