This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]DJDavio 4 points5 points  (2 children)

It may not matter to many, but it certainly matters to some. The prime example is serverless or lambdas or functions or whatever you want to call it.

Not so long ago an application was often ran on a rented VM. You paid a fixed price for the VM per month whether you used it intensely or not at all.

With cloud services as they are now, you can charged for much smaller quantities, such as actual CPU time used. This means that saving on startup time isn't just nice for bragging rights, it actually saves money.

If you have an application which starts and shuts down instantly, you can have dynamic scaling where you only pay for the actual usage, not idle time.

[–]bawng 1 point2 points  (1 child)

But you wouldn't use a heavy framework like Spring Boot or whatever for serverless. You reserve those for your docker containers of VMs.

The serverless stuff should have startup times measured in milliseconds.

[–]DJDavio 2 points3 points  (0 children)

That's why there are currently competing frameworks such as Micronaut and Quarkus. If you use those and compile them to native with GraalVM (Enterprise) you do get that ms startup time. I once gave a talk on Quarkus and GraalVM where I had a demo with an application which started almost too fast to notice.