3 ms·

>But in 2018, Google changes its pricing model, and my bill jumped to more like $1,800 per month. Presumably, Google has done the market research here and had

>But in 2018, Google changes its pricing model, and my bill jumped to more like $1,800 per month. Presumably, Google has done the market research here and had found that this level of pricing will end up maximizing revenue. It would be interesting to have a generally accepted model for these no money now, money later business models based on some measure of industry lock in. That way it would be possible to do the pricing at the start of a project rather than part of the way through when everyone had forgotten to budget anything. The Googles of the world get to know how much our projects are going to cost, why can't we at least get an idea?

TheRealPomax 7y ago
That presumes a project starts with people who intend to charge from the get-go, but defer that step to later. Rather than being started by folks who love what they're doing, getting funneled into a PM'ed project where the enthusiasm is curbed by "product viability", and then goes through a period of a few years where the original project folks rotate out until no one left is invested in how useful the product is, and a lot of folks are invested in how much money can be made by pivoting to a model that heavily monetizes on scoping down to purely the most used features used by its biggest, financially secure customers.
- takeda 7y ago
  That reminded me of a project where person leading it estimated that it will be cheaper and faster to use AWS, they only forgot all the hidden fees that AWS adds, most commonly the network fees (which are charged between AZs) or EBS etc. On top of that an instance that claims to have specific parameters won't deliver the same performance as supposedly equivalent physical machine, so you will need to use bigger instances etc. Ultimately the project did not have resources to set up DR version which was originally planned and still went way over the budget.

TheRealPomax 7y ago

That presumes a project starts with people who intend to charge from the get-go, but defer that step to later. Rather than being started by folks who love what they're doing, getting funneled into a PM'ed project where the enthusiasm is curbed by "product viability", and then goes through a period of a few years where the original project folks rotate out until no one left is invested in how useful the product is, and a lot of folks are invested in how much money can be made by pivoting to a model that heavily monetizes on scoping down to purely the most used features used by its biggest, financially secure customers.

takeda 7y ago
That reminded me of a project where person leading it estimated that it will be cheaper and faster to use AWS, they only forgot all the hidden fees that AWS adds, most commonly the network fees (which are charged between AZs) or EBS etc. On top of that an instance that claims to have specific parameters won't deliver the same performance as supposedly equivalent physical machine, so you will need to use bigger instances etc. Ultimately the project did not have resources to set up DR version which was originally planned and still went way over the budget.