Fork me on GitHub

@cfleming: Thanks for the link. I wouldn’t say it’s totally unusable, but it doesn’t seem like it’s suitable for something where you’d need realtime performance unless it’s kept warm.


But also, if one needs consistent API performance while keeping a low monthly cost, Linode and Digital Ocean are damned cheap. For something that’d fall under lambda’s free tier, they’d probably suffice.


I see lambda as more appropriate for something where I don’t necessarily care about realtime performance - say, firing lambdas off events for processing something - or where you need to be able to scale a particular function without having to care about provisioning capacity in advance.


But they’re clearly not a hammer I can use to hit every possible API with.


@ricardo: Right, but it’s a bummer that it’s so badly suited to the use case that I wanted to use it for.


However, I’ve done a bunch more testing today, and the good news is that Node is radically better for that use case.


I need to get to bed now, full details tomorrow sometime.