I was sure this was about some multiplayer game thing, but no, it's a crossword. Not entirely sure what they are even scaling here, I was expecting an article about a CDN..
Moving The New York Times Games Platform to Google App Engine
11–20 of 152 posts
Re: Moving The New York Times Games Platform to Google App Engine
#12Has anybody had successful experience deploying docker containers on appengine ? Last time i tried, i had such a bad experience in terms of deployment speed ( time to build the image, then upload it, then waiting for the stuff to deploy) that i reverted to managing my own gce instance.
But maybe i had bad luck..
Re: Moving The New York Times Games Platform to Google App Engine
#13Two things keep coming up while comparing GCP and AWS:
* This accomplishment would not have been possible for our three-person team of engineers with out Google Cloud (AWS is too low level, hard to work with and does not scale well).
* We’ve also managed to cut our infrastructure costs in half during this time period (Per minute billing, seamless autoscaling, performance, sustained usage discounts, ... )
Re: Moving The New York Times Games Platform to Google App Engine
#14Earlier quoted context omitted.
Have you tried the documentation for google's sdk? I stopped in disgust trying to track down what I needed and then trying to manage through multiple different admin interfaces.
I've been using google bits recently. I agree that the docs for e.g. all the python sdks need a lot of work. That said, boto3 has thorough docs, but I wouldn't consider them particularly well organized. I can only really navigate AWS sdk docs because I already know what I want to do, and can google the specific terminology
Are you talking about this Python SDK doc? https://googlecloudplatform.github.io/google-cloud-python/la...
Re: Moving The New York Times Games Platform to Google App Engine
#15"Due to the inelastic architecture of our AWS system, we needed to have the systems scaled up to handle our peak traffic at 10PM when the daily puzzle is published." WT... I had to reread this to make sure I didnt misunderstand... why not work on making the current arhictecture elastic?! #cloudPorn
The main story here is probably this line: "The system is generally at that peak traffic for only a few minutes a day". AWS charges by hour. Google by minute. If your peak traffic only last a few minutes, hourly billing is inflexible, simple as that.
AWS lambda charges by the 1/10th of a GB/CPU/second.
I'd bet they could have seen significant cost savings on AWS by migrating to lambda, and gotten continuous scaling to boot.
Re: Moving The New York Times Games Platform to Google App Engine
#16Has anybody had successful experience deploying docker containers on appengine ? Last time i tried, i had such a bad experience in terms of deployment speed ( time to build the image, then upload it, then waiting for the stuff to deploy) that i reverted to managing my own gce instance. But maybe i had bad luck..
Yes uploads are fast and you can spin up a VM directly from an image now
Re: Moving The New York Times Games Platform to Google App Engine
#17Earlier quoted context omitted.
The main story here is probably this line: "The system is generally at that peak traffic for only a few minutes a day". AWS charges by hour. Google by minute. If your peak traffic only last a few minutes, hourly billing is inflexible, simple as that.
AWS lambda charges by the 1/10th of a GB/CPU/second. I'd bet they could have seen significant cost savings on AWS by migrating to lambda, and gotten continuous scaling to boot.
Serverless is probably far too immature for companies like NYT.
Re: Moving The New York Times Games Platform to Google App Engine
#18"Due to the inelastic architecture of our AWS system, we needed to have the systems scaled up to handle our peak traffic at 10PM when the daily puzzle is published." WT... I had to reread this to make sure I didnt misunderstand... why not work on making the current arhictecture elastic?! #cloudPorn
The "inelastic" might have been a shot at AWS. When pressed, the AWS people do use phrases like "pre-warming", "over provisioning" and "advance notice" around their ELB/ALB setup and ECS. Google's cloud salespeople pitch that they don't require any of that.
Curious if the need for pre-warming ELB/ALB still applies. Last time this came up, an AWS employee mentioned it is no longer necessary (https://news.ycombinator.com/item?id=14052079), but would be nice if this was documented.
Re: Moving The New York Times Games Platform to Google App Engine
#19This reads eerily like a press release for GCP...
A third of the posts to HN are disguised press releases.
Re: Moving The New York Times Games Platform to Google App Engine
#20Earlier quoted context omitted.
The "inelastic" might have been a shot at AWS. When pressed, the AWS people do use phrases like "pre-warming", "over provisioning" and "advance notice" around their ELB/ALB setup and ECS. Google's cloud salespeople pitch that they don't require any of that.
Curious if the need for pre-warming ELB/ALB still applies. Last time this came up, an AWS employee mentioned it is no longer necessary ( https://news.ycombinator.com/item?id=14052079 ), but would be nice if this was documented.
Possible. It is still in the documentation: https://aws.amazon.com/articles/1636185810492479#pre-warming
The "advance notice" and "over provision" advice is still being given for things that could scale up fairly large. (where fairly large isn't anything that exciting, really)