3 ms·
It handles binary, but not well. http://forum.serverless.com/t/returning-binary-data-jpg-from-lambda-via-api-gateway/796 http://forum.serverless.com/t/returning
by idbehold 10y ago
It handles binary, but not well. http://forum.serverless.com/t/returning-binary-data-jpg-from-lambda-via-api-gateway/796 http://forum.serverless.com/t/returning-binary-data-jpg-from...
> Ideally long-running requests like that should be rearchitected to return fast and deliver the results asynchronously, right?
Ideally for whom? I can't think of an engineer who wouldn't rather do a simple request/response. It's certainly cheaper than spending the money to keep a connection open longer than 30 seconds, but far from ideal.
- revicon 10y ago>Ideally for whom? Anyone running on heroku works with a hard coded 30 second timeout on all web requests. It works fine for everyone there.
- idbehold 10y ago> It works fine You must have a different definition of ideal. I'm sure no one using Heroku would be upset if that limit was removed.