Author here :D
Gotta take a stance to draw graphs, right? Comparing no reserved instance with the automatic discount is simple and realistic in my experience.
I could make pricing graphs accounting for 25% of AWS reservations and 75% of automatic google discount. In my experience, that's the proportions we _may_ have in practise. It would still be the same conclusion. Google is massively cheaper.
I could make TCO pricing graphs, accounting for the thing from the last paragraph, plus the human time (500$/day) required to understand, pick and manage reservations. I didn't do all the computations but so far it points towards a negative ROI (compared to not reserving), unless the infrastructure is big enough to have the economy of scale (hundreds thousands dollar per year). (Note: I really don't want to go against all the HN/reddit crowd who drank the reservations marketing koolaid, so purposefully avoid to talk about the TCO pricing model publicly ^^).
Thus, in all scenarios, google instances are massively cheaper. YMMV.
Even with this tool we frequently make planning mistakes due to shifting business priorities or other reasons. Like - oh hay we have to upgrade our database instance but that needs a newer version because only the newer versions support something we need (i.e more than X GB ram). So engineering needs to modify the app to support the newer version.(Oh by the way AWS has a boatload of subtle restrictions like that.)
In this case we were sitting on a RI till EOY and for some reason you can't resell RDS RIs like normal ones (another subtle restriction) so we couldn't even partially recoup costs. Sometimes if you haggle with AWS Enterprise Support you can get them to help out if you're spending the money elsewhere but it's a pain. Good luck if you don't pay for that though (which itself is 15k a year or more).
And there is a 3rd competing tool that I can't seem to remember the name.
The calculus involved with matching RIs to forecSted demand in a dynamic growing workload is NP complete. And any inefficiency delta pays AWS. There's a small part of the curve where your savings is minimal if you don't match perfectly, it it easily goes to negative on the RI change.
You have to get pretty big to get discounts from published prices, far bigger than $1M/year, more like $1M/month.
To get a rep (that's unrelated), you have to pay full support which is about 10% per month (with a high minimum fee).
RDS instances with Postgresql.
Let me know if there are any others.
Like AWS?
I see.
In both cases, there are partners that enrich these ecosystems.
Most alpha services do not yet have gcloud support.
I'm PM for another Google Cloud database (not Cloud SQL), but will share this with the team.
Postgres
Integrated domains (a la R53)
S-N/E/Q-S
I'm generally comparing AWS to colocation, not other IaaS offerings.
Google's Lambda equivalent is currently in Alpha. That said, there are bits like Cloud Logging and AppEngine that offer unique-to-Google functionality that's somewhat comparable.
(Work on Google Cloud)
http://db-engines.com/en/system/Amazon+DynamoDB%3BGoogle+Clo...
This is a bit outside of my expertise, but that page mainly points out that DynamoDB supports 3 more language-specific SDKs, while lacking ACID and what appears to be native cross-region replication (through Lambda). Until recently, Datastore was coupled with AppEngine that might explain it.
Would love to hear more thoughts from you.
(work at Google Cloud)
Is Datastore Spanner?
Datastore and Bigtable have different characteristics and use cases; see https://cloud.google.com/storage-options/ for an overview.
Datastore is a document database (compare it to MongoDB), while Bigtable is a wide-column store (compare it to HBase or Cassandra).
> Is Datastore Spanner?
Datastore is built on Megastore, which builds on Bigtable. :-)
I am the PM for Google Cloud Bigtable.
You can think of Hbase as a clone of Bigtable, if that helps. Bigtable is actually exposed through the Hbase API. /u/mbrukman here is the PM for Bigtable.
[0] https://cloudplatform.googleblog.com/2016/03/financial-servi...
Lambda and Cloud Functions are competitors, though there are some things you could do with Lambda + API Gateway that you can't quite do with Cloud Functions just yet (pretty narrow scope, though). I prefer the environment for Cloud Functions, subjectively.
There's PubSub, Cloud Logging, Firebase (including Firebase Messaging), and all 3 don't really have a great direct AWS equivalent.
Take a look at the AWS/GCP equivalents at [1]. Mostly full coverage, although, again, some services work differently (usually better I hope!).
Email is indeed handled through either SendGrid or Google Apps [0]. Spam reasons I believe.
[0] https://cloud.google.com/compute/docs/tutorials/sending-mail...
Do you know how long the Dataflow processing will take? You may be able to estimate the length of the full-size process (assuming it's batch rather than streaming) by running on a small data sample to see how many vCPU hours it takes and estimate from there, assuming your data takes a uniform amount of time to process.
Since Dataflow is running code that you wrote, it doesn't know how complex your processing will be for any given value, so it's hard to give any reasonable estimate. In general, automatically predicting how long an arbitrary piece of code will take to run on a given input is even harder than the Halting problem (https://en.wikipedia.org/wiki/Halting_problem), which is already undecidable.
Details on Dataflow pricing: https://cloud.google.com/dataflow/pricing
Pricing calculator to estimate cost for Dataflow and other products: https://cloud.google.com/products/calculator/
Hope this helps!
Another way to look at Dataflow pricing as it related to this type of technology. Let's just assume for a second Dataflow and other similar technologies execute your pipeline on your data within the same resource-time amount.
Dataflow lets you set an upper bound on these resources, and lets you auto-scale, with essentially per-minute granularity. Alternatively, you can create a cluster of fixed resource amount. Cost of Dataflow is $0.01 per hour per CPU, in addition to those resources.
Dataflow's model hence either guarantees 100% resource efficiency, or you specifically opt into the upper bound of spend. A deployment model that lets you "spin up a cluster and pay for it" is intrinsically less efficient.
I wrote a blog on this WRT BigQuery, but Dataflow is right there [0].
[0] https://cloud.google.com/blog/big-data/2016/02/understanding...
(Work on Google Cloud)
But does it support commas?
While I agree that Google's pricing model is superior, the author's position on reserved instances accounts for ~40% of the cost difference.
In a drag race between instances AWS tends to lose. If you value the enormous feature and service surface-area that AWS provides it's a different story. Either way we win; both companies will engage in a brutal price and feature war for many years to come.