[LRUG] Feet up/hands off/phone off managed hosting/peace of mind

[Frederick Cheung]

Also consider automation - automated failovers can be tricky to get right but will happen faster than any human based option. With a platform like heroku that's just part of the service, but it's easy enough to do for application servers on AWS with autoscaling. 

Database failovers can be trickier. Mongo pretty much takes care of itself if you use a replica set, for relation databases we use amazon's RDS which takes care of this (for the record we had a database failure around 4am on boxing day last year. Other than a flurry of airbrake errors for a few minutes I barely noticed)

Fred


On 24 September 2014 at 12:18:54, Tim Harding (tim.harding at gmail.com) wrote:
> Yes! Though I think that managing a team that costs more than our revenue
> would probably cause more stress than having to leave my phone on in case
> Pingdom alerts. ;)
>  
>  
>  
> On 24 September 2014 12:04, Don Werve wrote:
>  
> >
> > On Sep 24, 2014, at 19:58 , Gabe da Silveira wrote:
> >
> > > Another strategy to consider: hire at least one developer in Sydney, one
> > in London, and one in San Francisco ;)
> >
> > This is one of the benefits of building a distributed team — on-call
> > schedules just become part of the workday.
> > _______________________________________________
> > Chat mailing list
> > Chat at lists.lrug.org
> > Archives: http://lists.lrug.org/pipermail/chat-lrug.org
> > Manage your subscription: http://lists.lrug.org/options.cgi/chat-lrug.org  
> > List info: http://lists.lrug.org/listinfo.cgi/chat-lrug.org
> >
> >
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> Archives: http://lists.lrug.org/pipermail/chat-lrug.org
> Manage your subscription: http://lists.lrug.org/options.cgi/chat-lrug.org
> List info: http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>