On the morning of February 28, 2017, Amazon Web Services (AWS) experienced an outage in the US-EAST-1 Region among systems relying on its Simple Storage Service (S3) cloud offering. The event wreaked havoc on thousands of websites. The cause? A fat-finger mistake by a human in a line of code that took more servers offline than desired.
“Removing a significant portion of the capacity caused each of these systems to require a full restart,” noted Amazon in a blog post. “While these subsystems wer
Also: Trading Technologies is developing an OMS for the sell side and Orbital Insight is embracing a platform-as-a-service model.Subscribe to Weekly Wrap emails
- Wavelength Podcast Episode 141: Brexit and Blockchain and Data, Oh My
- Nasdaq, User Groups Fire Opening Salvoes in Looming Battle Over SIP Data Fees
- JPX Mulls Pooling Content into Data Lakes
- Wavelength Podcast Episode 142: AWS Talks Cloud Adoption in the Capital Markets
- Alt Data’s Ethical Day of Reckoning