News for hackers. Stuff that matters.
Re:A million-dollar engineering problem by sly010 on Thursday March 16, 2017 @02:14PM (#13887415)
The simplest one might be to convince a company to reserve 3 years worth of AWS resources and paying upfront. I am in this situation right now, but and it's a tough pill to swallow.

I decided that all of my personal projects will be GCE. It is much more cost efficient already and Google will soon allow me to commit to future usage and pay my commitment as I go (Right now AWS forces you to pay upfront to get the same discount (~50%))

Re:A million-dollar engineering problem by QuinnyPig on Thursday March 16, 2017 @04:00PM (#13888617)
With a couple of exceptions, 3 year RIs are a poor move.

You're locking in pricing, and opting out of both newer instance classes and future price reductions during that time period.

Generally, they're only useful for "that database we WILL NEVER MOVE," or if you're writing portions of your cloud spend as CapEx and want to amortize depreciation.

Re:A million-dollar engineering problem by sly010 on Thursday March 16, 2017 @04:19PM (#13888798)
I agree on AWS it's a hard move. On GCE, however, you would be buying CPU and memory units, not machines, which to me is much more appealing. Even if the the price drops 50% every year, i would break even.