3 ms·
EC2 or on-premise you need monitoring to detect issues before they become issues. A single drive on a single server failing should never cause a production out
by jabart 4y ago
EC2 or on-premise you need monitoring to detect issues before they become issues.
A single drive on a single server failing should never cause a production outage.
A lot of configuration issues can be tracked down to self-contained deployments. Does that font file or JRE really need to be installed on the whole server or can you bundle it into your deployment.
Our deployments use on-premise and EC2 targets. The deployment script isn't different, only the IP for the host is.
Now, I will say if I can use S3 for something I 100% will. There is not an on-premise alternative for it with the same feature set.
- orangepurple 4y agoFine, but RAID-Z2 in a dedicated server is good enough or overkill for most people and it's free.
- jabart 4y agoHackerNews went down because two SSDs in a mirror went down at the same time. This was due to a hours on SSD bug. While Raid-Z2 works, and provides great reliability, two-servers replicated, both with raid-z2 and a nightly offsite backup and as long as you are testing your backups it's a solid plan.
- bsder 4y agoAnd AWS goes down about once a year because US-East-1 has some weird failure. Your point? The point of DevOps is "Cattle, not pets." Put a bullet in your server once a week to find your failure points.