The latest Tweets from App Engine (@app_engine). Hey everyone — we’ve updated our handle to @googlecloud, hit us up there! Love, Google App Engine. Google Cloud Platform outage brings down Spotify, Snapchat, and more Google App Engine: Build and deploy applications on a fully. Snapchat, Spotify, Discord, and Pokémon Go all went down for portions of the Google Cloud’s app engine took out several popular apps.
|Published (Last):||5 December 2011|
|PDF File Size:||1.5 Mb|
|ePub File Size:||10.68 Mb|
|Price:||Free* [*Free Regsitration Required]|
Last week I saw this post which reminded me a lot of our experience with App Engine a few years ago. But first some background, our startup uses a very complex set of servers hosted almost everywhere thru the years… From Azure, to AWS, Linode, Digital Ocean and many others… The reason for this complexity relates to our core product which requires domain specific servers.
To simplify our initial launch and to scale properly we chose App Engine. The main goal for picking PaaS over IaaS is simplicity.
Incidents reported in the last 365 days
We saw it as a shortcut so we can focus on our mobile platform and not on managing servers. For the first couple of years things worked outwge, we had some issues to be sure e. Our servers were down for hours and the logs were completely cryptic.
We still liked app engine after that and we even did a talk at JavaOne where we discussed how helpful it has been for us to scale our business rapidly.
To prevent issues like the downtime we had from recurring we decided to pay for gold support extra USD per month so such issues will not recur. A google rep wrote to me trying to arrange a call but nothing really happened due to scheduling conflicts and I never physically talked to a google rep in relation to the gold support.
Google App Engine Incident #16008
I did meet with a couple of Google reps at their local offices before upgrading to gold and had some discussions about app engine with them but mostly abstract line of business talks.
The problem is that this is a needle in a haystack! Naturally we called on Gold support, to appenvine we even sent our full project source code. They concluded after reviewing their logs that the problem was on our side….
This was a disaster since we were getting a bill so large it nearly wiped our revenue. Being bootstrapped and in the early stages of monetization appengije had the potential of sending us into bankruptcy. The billing eventually went down but to this day we have no way of knowing which one of our changes fixed it.
Google Cloud issue causes outages for Snapchat, Spotify and others – CNET
Clearly something in our code broke, right? I will take some blame, mostly for picking app engine but not for this issue. When I get a phone bill I get itemized details on why the charges were made. Google did no such thing.
They list an opaque item within the line items and ouage information about the actual source or a way to debug this at least not back in However, having said that migrating away from app engine gave us HUGE unforeseen advantages:. As I wrote the original apepngine someone asked about AppScale. When you do something you need to honestly and methodologically examine your failures and see how you can avoid them in the future:.
Our annual spend on infrastructure has kept relatively steady despite business growth. Sign in Get started. Never miss a story from Hacker Noonwhen you sign up for Medium. Get updates Get updates.