7 ms·
Sure but at a very different price point.
by qaq 8y ago
Sure but at a very different price point.
- scarface74 8y agoAnd too often, developers (smaller companies) and ops (larger companies) time is considered free because they are salaried and are expected to work more than 40-45 hours per week. Yes, earlier in my career I would have accepted that, but I’ve successfully pushed back a few times and said I won’t babysit a process/server etc but I will design a method where it is auto healing, autoscaling, etc.
- matwood 8y agoAs someone who has been both the server baby sitter and implementor of auto-healing/scaling, it still puts a smile on my face when a server fails a health check, AWS kills it, starts another one, and moves the work over. All with zero downtime. I just see the emails in the morning that it happened. The other huge benefit of building this process is we can use dirt cheap spot instances with near abandon. For me, any infrastructure that I can't treat as cattle is on my hit list.
- qaq 8y agoWhen AWS is failing over RDS PG there is def nonetrivial downtime
- matwood 8y agoAnd? You think running your own database is going to have better uptime and scalability than something like Aurora? If something like DB HA is important, I think it's much easier in AWS for a company with a smaller engineering department.
- qaq 8y agoI am just pointing out that no downtime applies to failing over very specific services. In general AWS had pretty horrible track record on outages. A single top tier DC has way better uptime vs AWS Region.
- scarface74 8y agoAn AWS region or an AWS availability zone? You should always make everything multi-AZ whenever feasible.
- qaq 8y agoRegion. The multi Region thing is partial BS too if US East has a total failure there is not enough spare capacity to absorb all of US East compute in other Regions.