Earlier quoted context omitted.
Not to be that guy, but why lambdas? I'm genuinely curious. I've never found the "cost savings" (big air quotes) worth it in comparison to the increased configuration/permissions complexity. Especially when Fargate exists, where you can just throw a docker container at AWS, what do Lambdas add? The zero scaling?
Your mileage may vary, but I think in majority of the cases Fargate is going to be significantly more expensive than Lambda.
Google Cloud Spanner is now half the cost of Amazon DynamoDB
161–170 of 371 posts
Re: Google Cloud Spanner is now half the cost of Amazon DynamoDB
#162Re: Google Cloud Spanner is now half the cost of Amazon DynamoDB
#163I'm torn because I have really liked Google offerings in the past (I'm pretty locked in on gmail, I have different things running on GCP already, etc). But I've also been feeling burned a bit by Google suddenly ending services. I had all my domains happily in Google domains until they recently sold it suddenly to Squarespace, who I'm not interested in dealing with. My phone is a Google Pixel and I was using the Googl…
Re: Google Cloud Spanner is now half the cost of Amazon DynamoDB
#164Earlier quoted context omitted.
> I will say that it does show a vote of confidence to say that Photos, Gmail and Ads use GCP infra, I'm not sure? I guess I'm mostly not sure what "gcp infra" means there. The blog post says "Spanner is used ubiquitously inside of Google, supporting services such as; Ads, Gmail and Photos." But there's google-internal spanner, and gcp spanner. A service using spanner at Google isn't necessarily using gcp. (No clue a…
Surely in a post about Google Cloud Spanner, all examples mentioned use Google Cloud Spanner? It would be moot listing them as examples if they would not: so my assumption is they are all using GCP infra already for Spanner. I really want to give Google the benefit of the doubt: but it doesn't help that they did not write that eg Gmail is using "Cloud Spanner." They wrote that it uses Spanner.
Re: Google Cloud Spanner is now half the cost of Amazon DynamoDB
#165“ According to the Amazon Prime Day blog post, DynamoDB processes 126 million queries per second at peak. Spanner on the other hand processes 3 billion queries per second at peak, which is more than 20x higher, and has more than 12 exabytes of data under management.” This comparison seems to be not exactly fair? Amazon’s 126 million queries per second was purely for Amazon-related services serving Prime Day generatin…
From the AWS blog post they referenced- > DynamoDB powers multiple high-traffic Amazon properties and systems including Alexa, the Amazon.com sites, and all Amazon fulfillment centers. Over the course of Prime Day, these sources made trillions of calls to the DynamoDB API. DynamoDB maintained high availability while delivering single-digit millisecond responses and peaking at 126 million requests per second. Amazon w…
Worst case scenario, it's Google you're buying, not a random startup etc.
Re: Google Cloud Spanner is now half the cost of Amazon DynamoDB
#166Earlier quoted context omitted.
Except for projects for which NoSQL is a better fit than a RDBMS, no? If I'm writing a chat app with millions of messages and very little in the way of "relationships", should I use Postgres or some flavor of NoSQL? Honest question.
Postgres; the schema is still structured. But even if you want something less rigid, Postgres has a jsonb type and great operators for querying json.
Re: Google Cloud Spanner is now half the cost of Amazon DynamoDB
#167Re: Google Cloud Spanner is now half the cost of Amazon DynamoDB
#168Re: Google Cloud Spanner is now half the cost of Amazon DynamoDB
#169Re: Google Cloud Spanner is now half the cost of Amazon DynamoDB
#170Cool, too bad I can't rely on Google suddenly deprecating this service.
An internal version has been used within Google since ~2012 and the GCP version has been available since 2017. It's used extensively within Google. It's not going to be deprecated any time soon.