Hacker News Reader

That's the limitation for data related worker tasks. The iron.io can be alternative (they offer 512 MB https://try.iron.io/pricing-worker-monthly/)

That would be OK for some ML applications if the framework itself would not be included in the deployment package.

There are workarounds for that, f.e. on startup loading code from an s3 bucket (https://hackernoon.com/exploring-the-aws-lambda-deployment-l...)

That workaround is for the 50MB limit on zip files, not for the 250MB limit :)

No, you get another 500 MB of tmp space you can use at runtime. This workaround does work.