apex / up

Deploy infinitely scalable serverless apps, apis, and sites in seconds to AWS.
https://up.docs.apex.sh
MIT License
8.8k stars 380 forks source link

CloudFlare workers #620

Open tj opened 6 years ago

tj commented 6 years ago

https://blog.cloudflare.com/cloudflare-workers-unleashed/ might not be possible but investigating...

kevinsimper commented 6 years ago

Cloudflare could be a cool thing in front of lambda as a way to collect multiple API gateways on the same hostname.

You are only allowed 1 mb of space in that service-worker file

https://developers.cloudflare.com/workers/writing-workers/storing-data/

pctj101 commented 6 years ago

Would definitely be of interest

zackbloom commented 6 years ago

I'm a member of the Workers Engineering team. We will happily adjust any and all of these limits if Apex needs them changed.

kevinsimper commented 6 years ago

@zackbloom Would there be some trial of Cloudflare workers? There seems no way to try out cloudflare workers without incurring a cost of $5 just for the base.

tj commented 6 years ago

@zackbloom thanks for dropping in :D — let me know if this isn't the case, but it seems like CloudFlare Workers might not be suitable for Up since I need to launch background processes (Go binary which in turn launches the user application).

kevinsimper commented 6 years ago

@tj cloudflare could be the domain in front of other cloud functions that does not allow putting it behind a domain like Google Cloud Functions or if you don't want to move the domain to AWS and doe the complicated domain setup (if you already have you domain on cloudflare).

zackbloom commented 6 years ago

@tj It sounds like we have two problems:

  1. We need to support Go.
  2. We need to support persistent applications.

1 is (relatively) easy, we'll have WebAssembly support shortly. 2 is tougher. In the spirit of 'serverless' we haven't found that many other persistent applications yet which gain value from living at the edge of the network (other than maybe data stores). Most other things seem to be digestable into the idea of requests, map/reduce actions, or something similar.