Just seen the Workers Unbound. Looks great. I see it’s pitched as a rival specifically to AWS Lambda in the post. Which makes sense, it’s serverless but faster and cheaper.
So based on that comparison, a few questions (which I appreciate may not be answerable if it’s currently private):
Is there a limit on deployment size? A Worker can be up to 1MB, whereas a Lambda zip can be 50MB (zipped). Does it keep the 1MB limit, or move to a Lambda-competing larger size?
Is there any /tmp space available? Again, Lambda has some kind of storage available for temporary operations on disk, like downloading a file, processing it etc.
Is there still the same issue Workers has where a Worker can not call another Worker (within the same zone)? As I read it, you couldn’t have e.g. sub1.example.com call sub2.example.com. Which is useful if you have e.g. api.example.com and want to call that API from other domains. Based on Issue With Worker-To-Worker HTTPS request Since with Lambda (with API Gateway) you can call you own subdomains.
Thanks. (Sounds like I’m promoting Lambda here, which I’m not! It would be great to have something faster and cheaper. Just trying to understand where the issues may arise)