Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Prime Day 2017: 12.9M DynamoDB requests per second

aws.amazon.com

Post reply on HN
Print view View original

41–50 of 67 posts

Re: Prime Day 2017: 12.9M DynamoDB requests per second

#41

Post by puzzle »

ra7 wrote: post #31
plandis wrote: post #18

Earlier quoted context omitted.

According to this Amazon job listing [1], DynamoDB isn't even the biggest (in terms of throughput) data store that Amazon uses. [1] https://www.amazon.jobs/en/jobs/447605/systems-engineer

> SABLE is at the core of Amazon.com retail infrastructure. It more than 400 billion requests per day from Amazon.com websites, Web Services, and internal Amazon systems. Wow!

Three years ago or more, Bigtable served that much traffic in less than fifteen minutes: https://twitter.com/akpurtell/status/463747917782589441

Re: Prime Day 2017: 12.9M DynamoDB requests per second

#42

Post by ElectronShak »

Artemis2 wrote: post #33

Something I appreciate very much with AWS is how much dogfooding Amazon does. In contrast, Google has said in the past that GCP is not used by Google engineers (and it shows, occasionally GCP goes down but actual Google products do not!). There is also no clear indication that Microsoft is actively using the public deployment of Azure.

>dogfooding

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.

Re: Prime Day 2017: 12.9M DynamoDB requests per second

#43

Post by verst »

Artemis2 wrote: post #33

Something I appreciate very much with AWS is how much dogfooding Amazon does. In contrast, Google has said in the past that GCP is not used by Google engineers (and it shows, occasionally GCP goes down but actual Google products do not!). There is also no clear indication that Microsoft is actively using the public deployment of Azure.

Microsoft employee / Developer Advocate for Azure here.

We run a lot of services and applications on public Azure. This trend is only increasing.

Re: Prime Day 2017: 12.9M DynamoDB requests per second

#44

Post by noncoml »

verst wrote: post #43
Artemis2 wrote: post #33

Something I appreciate very much with AWS is how much dogfooding Amazon does. In contrast, Google has said in the past that GCP is not used by Google engineers (and it shows, occasionally GCP goes down but actual Google products do not!). There is also no clear indication that Microsoft is actively using the public deployment of Azure.

Microsoft employee / Developer Advocate for Azure here. We run a lot of services and applications on public Azure. This trend is only increasing.

Some examples?

Re: Prime Day 2017: 12.9M DynamoDB requests per second

#46

Post by rprime »

jonhohle wrote: post #28
plandis wrote: post #18

Earlier quoted context omitted.

According to this Amazon job listing [1], DynamoDB isn't even the biggest (in terms of throughput) data store that Amazon uses. [1] https://www.amazon.jobs/en/jobs/447605/systems-engineer

I miss SABLE. I like it better than DDB, but I'm probably in the minority there. It made building high throughput services easy. I'm somewhat surprised it mentioned publicly.

> I'm somewhat surprised it mentioned publicly.

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.

Re: Prime Day 2017: 12.9M DynamoDB requests per second

#47

Post by chimeracoder »

Artemis2 wrote: post #33

Something I appreciate very much with AWS is how much dogfooding Amazon does. In contrast, Google has said in the past that GCP is not used by Google engineers (and it shows, occasionally GCP goes down but actual Google products do not!). There is also no clear indication that Microsoft is actively using the public deployment of Azure.

> In contrast, Google has said in the past that GCP is not used by Google engineers (and it shows, occasionally GCP goes down but actual Google products do not!)

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.

Re: Prime Day 2017: 12.9M DynamoDB requests per second

#48

Post by dx034 »

pentelian wrote: post #26

When I read that I thought holy heck... on DynamoBD, if it's not a case study about Amazon then that company is in serious financial trouble.

I'm sure that any external client using >1bn queries per day would get a very different pricing from the one advertised.

Re: Prime Day 2017: 12.9M DynamoDB requests per second

#49

Post by dx034 »

phamilton wrote: post #38
uji wrote: post #24

Is Amazon comfortable enough to create single point of failure. What if DDB goes down assuming they run same stack for both retail and AWS?

> What if DDB goes down 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 dat…

How do they structure regions? Is amazon.co.uk running on different regions than amazon.com? Or everything distributed globally?

Re: Prime Day 2017: 12.9M DynamoDB requests per second

#50

Post by mabbo »

LiteskinKanye wrote: post #5
delecti wrote: post #3

Earlier quoted context omitted.

After hearing pagers going off throughout that day, it's reassuring to hear someone on the outside say everything went flawlessly.

What's the DevOps duty look like? Anytime you just see a page and root cause it and just tell your higher-up they are SOL

I can't speak for the whole company, but I've done 5 peaks (holiday seasons) as an SDE in the Warehouse/Delivery orgs.

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.

Post reply on HN