3 ms·
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,
by detaro 7y ago
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 7y agoIn that case that falls into the latter exception I made where you manage the host; albeit the management is just “buy an instance”.