> Are there any other options around? Are there any other outstanding issues in developing for for Lambda? I'm not sure how AWS Lambda handles the charging of

> Are there any other options around? Are there any other outstanding issues in developing for for Lambda? I'm not sure how AWS Lambda handles the charging of network latency (or failure) case of downstream external service dependencies but that is one of our biggest problems. ie pull/scrape architecture. The push portion (ie events) of our architecture is an obvious fit but that is already taken care of quite nicely. We interact with hundreds of web services (REST APIS, SOAP, etc) that are actually external from us. Its unclear if or how Amazon charges you for a slow external service (I would imagine its particularly bad if the code is blocking IO) or if that is even possible. I do know spawning a whole bunch of servers to connect to a single REST API endpoint is damn slow. I have feeling Lambda for our case is probably not a good one? Obviously for data processing I can see it but that is not a challenge we have. In an ideal world our downstream (or I guess it could be called upstream...) dependencies would contact us but... that sadly isn't the case particularly for adhoc stuff.