Hacker News new | past | comments | ask | show | jobs | submit login

Its just an abstraction though. And it falls apart and becomes full of implementation details when the actual fact that its running on a warmed up or cold server causes issues



It is, but once you agree on the context it provides, it can be a word that is useful when describing how you plan to deploy some section of code.

We use Lambdas for a bunch of different async work tasks like PDF generation and such. Warm or cold doesn't matter at all for us.

If you're trying the super 'serverless' approach of using AWS API services backed by Lambdas, then yeah, warm/cold will definitely matter.


When I think "serverless" I think this: http://unhosted.org/

That describes a model where a web paged is permanently cached in a browser's data. Effectively reducing the server to a binary distribution system.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: