Amazon's cloud service crash permanently lost data. Think this has implications for EDA?
Today, MSNBC’s Technolog carries an article by Henry Blodget that discusses another aftermath of the Amazon EC2 (Elastic Compute Cloud) services failure: lost data. The article quotes a letter from Amazon stating:
“A few days ago we sent you an email letting you know that we were working on recovering an inconsistent data snapshot of one or more of your Amazon EBS volumes. We are very sorry, but ultimately our efforts to manually recover your volume were unsuccessful. The hardware failed in such a way that we could not forensically restore the data.”
As a result, one client of Amazon’s EC2 services, Chartbeat, sent this note to its customers:
“Approximately 11 hours of historical data wasn’t recoverable and will appear as small gaps in the timeline. Our development team is also hard at work to limit the impact of any future AWS interruptions.”
Now consider how the letter might have been worded if Chartbeat were an SoC design house:
Related Semiconductor IP
- NFC wireless interface supporting ISO14443 A and B with EEPROM on SMIC 180nm
- DDR5 MRDIMM PHY and Controller
- RVA23, Multi-cluster, Hypervisor and Android
- HBM4E PHY and controller
- LZ4/Snappy Data Compressor
Related Blogs
- What does Amazon's multiday cloud outage mean for EDA cloud services?
- EDA 'co-opertition' - a new era or more lip service?
- EDA in the Cloud: OneSpin says your design is secure
- Scaling EDA in the Cloud
Latest Blogs
- lowRISC Tackles Post-Quantum Cryptography Challenges through Research Collaborations
- How to Solve the Size, Weight, Power and Cooling Challenge in Radar & Radio Frequency Modulation Classification
- Programmable Hardware Delivers 10,000X Improvement in Verification Speed over Software for Forward Error Correction
- The Integrated Design Challenge: Developing Chip, Software, and System in Unison
- Introducing Mi-V RV32 v4.0 Soft Processor: Enhanced RISC-V Power