Prime Day 2017: 12.9M DynamoDB requests per second
aws.amazon.com
aws.amazon.com
Big projects are still built out of GCP mostly for cost reasons - google doesn't give itself a discount on gcp
The term "dogfooding" is a tech slang for the use of one's own products. In some uses, it implies that developers or companies are using their own products to work out bugs, as in beta testing. One benefit of dogfooding is that it shows that a company is confident about its products.
I didnt know what the term meant so had to look it up. Yeah, I agree.
We run a lot of services and applications on public Azure. This trend is only increasing.
I suspect 343 Industries (Microsoft Studio behind the latest Halo games) also uses it. They are one of the big users of Project Orleans https://dotnet.github.io/orleans/, a C# distributed actor framework. Most of their documentation and samples are shown using the framework in Azure.
Amazon (the shopping website) is generally online when AWS goes down, so that doesn't really indicate anything.
Also, GCP is directly modeled after the infrastructure that Google uses to develop internally. I don't know if it's actually the same exact infrastructure that they sell as GCP, but it's not like they're developing GCP fresh and selling it.
(My impression is that Amazon operates out of a different region than the public AWS. Much like GovCloud isn't the same as the public regions. Hence an AWS region being impacted doesn't necessarily impact Amazon itself since their separately operated.)
However, not all of Amazon.com has migrated to AWS.
[0] https://medium.com/netflix-techblog/global-cloud-active-acti...
(edited to correct size - was 52 pB not 520 pB...)
The key to remember about Amazon DevOps is that Developers are also DevOps. My team would usually share a dedicated DevOps team with 3 to 6 other teams- usually rotating front-line on-call duty between 2 or 3 people in the US and 2-3 in India. That DevOps person has the job of: what is the problem? Do my teams own this problem (if not, redirect to the right place)? Do I know how to immediately fix this? If not, for which of my teams do I page the on-call SDE?"
When you have a great DevOps team, SDE oncall duty is a walk in the park. But DevOps people take time to become great- and many of them are also applying for transfers to SDE roles.
Overall, each org decides how on-call/DevOps is. If time and effort and spent investing in stable software, it's easy. If other priorities get in the way, things can get bad.
Overall things went well for Amazon, but flawless? I think not.
You could argue that the original title is misleading, because you would've thought that it was some advertisement (though isn't anything touting large numbers a form of advertising?).
Is Amazon entirely based out of Dynamodb nosql ?
I guess it explains why I am not able to find any information related to SABLE. Are you able to release anything related to it? It seems really interesting.
Wow!
It's worth clarifying that question. What does "Go Down" mean? One region is down? Is it a bad software bug?
The database itself is fault tolerant. Nodes can go down all day without any real consequence. Each region is isolated, so a failure in one region won't affect other regions.
I guess I'm at a loss for the type of failure with DDB that would make it a SPOF, especially more than other datastores.
12,900,000 / second - WOW. Too bad the request rate was probably closer to 15,000,000 / second and you just abandoned everyone else.
Here's more on the report: http://www.consumerwatchdog.org/story/your-amazon-sale-item-...
Effectively the FTC is required to do its due diligence and the FTC has not accused Amazon of anything. It's some third-party group making the accusation.