Hacker News Reader

Comment by seanmck | Hacker News Reader

The core second price at the top is incorrect. The per-second prices for cores and GBs are the same: $0.0000125. We are getting that fixed now.

View on HN

So what you are saying is the calculation for 1 core, 1GB of memory for 1 month would be:

  0.0025 create + (0.0000125 1 core/second + 0.0000125 1GB memory/second) * 86400 seconds/day * 30 days/mo = $64.8025/mo

Is that correct? $64.8025 per month is pretty steep for 1 core and 1GB of memory, I guess this is targeted at short-lived jobs.

Yes, the billing is specifically targeted around per-second execution. The containers can start within a few seconds, they allow for customization of CPU cores and memory, and they allow you to focus entirely on your container without having to worry about any VM management. Traditional VM-based infrastructure is still the way to go for long-running applications. This just opens a new avenue into using containers in the cloud.

What would be some example use cases for this?

Off the top of my head, I'd say anything you might use Lambda and it's ilk for.

Off the top of my head, this could be used for backups, database migrations, auditing software, report generations, email blasts, CPU/memory intensive operations... The possibilities are endless because the execution layer is just a container, so you're not limited on what exactly is being run inside it.

You also incorrectly use "GB-s" in the Core Duration calculation in the Pricing Example:

"30 Create Requests * 300 seconds * 1 Core * $0.0000125 / GB-s = $0.1125"

Good catch - thanks.

Just FYI, the text still has the rounded number too:

> You are charged $0.000013 for every Core-s used

Reply on news.ycombinator.com