News for hackers. Stuff that matters.
Re:Summary of the Amazon DynamoDB Service Disruption by _alex_ on Wednesday September 23, 2015 @08:41AM (#10264637)
CloudWatch is a monitoring service that AWS offers publicly. It is different from the monitoring service that AWS services use internally.

source: was on an AWS service team for several years

Re:Summary of the Amazon DynamoDB Service Disruption by berkay on Wednesday September 23, 2015 @12:14PM (#10265927)
It's still a problem even if it's not the internal monitoring system. Customers use CloudWatch to detect problems with DynamoDB and get notified. This dependency means customers may not get notified if CloudWatch does not work as expected due to a DynamoDB problem.
Re:Summary of the Amazon DynamoDB Service Disruption by sharpy on Wednesday September 23, 2015 @07:54PM (#10269057)
There are different forces at play.

On one hand, one can design a service with minimum dependencies to survive other services' outages, but that means duplication of effort and increased cost, as well as slower delivery of features. Or one can focus on adding value.

It seems though, from the update, that CloudWatch is going to have some sort of caching for most recent data.

Re:Summary of the Amazon DynamoDB Service Disruption by ckozlowski on Wednesday September 23, 2015 @01:08PM (#10266310)
I follow. In this case though, I was thinking of the customer's monitoring tools. Their first action would be to try a diagnose themselves.

But good to know! Thanks!