A commonly made distinction between the two is that Heroku still exposes instanc... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		detaro on June 1, 2019 \| parent \| context \| favorite \| on: Stripped-down Kubernetes on the Raspberry Pi A commonly made distinction between the two is that Heroku still exposes instances to you: You buy a number of "dynos". Whereas a "serverless" solution doesn't, e.g. lambda just spins up workers as needed and bills you for the CPU time used.

pushpop on June 1, 2019 [–]

In that case that falls into the latter exception I made where you manage the host; albeit the management is just “buy an instance”.

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