Building highly available and fault tolerant sites on a budget
You've created your great new website or webapp, launched it and are now taking a well-deserved vacation... until your inbox starts screaming with SERVER DOWN emails. As you drop beach towels and scramble for your laptop, cold sweat dripping from your forehead, you're frantically trying to get that server back and find what the hell happened, hoping, beyond hope, that you'll manage to fix it in time before both your users and your SO start cursing you for the trouble you've caused them.
Or, you could decide to build a bit of redundancy into your app's architecture, just enough to keep the lights on until you come back to work on Monday.
If the alternative version sounds more appealing to you, come to this talk and learn how to easily build systems that are fault-tolerant enough, and available-enough that for you to have a peace of mind knowing that you don't need to respond immediately to such a crisis. We'll balance the level of availability versus the cost and complexity involved, and go through some typical and simple scenarios that may apply to you.Slides Rate the talk
Senko runs a web development shop by day and experiments with programming languages by night. Programmer since the days of C64, for the past few years he's worked on all kinds of web application projects.
Lately he spends his days with an email client and spreadsheet more than a code editor, and he's as likely to rant about processes, methodologies and go-to-market strategies as to rant about generalized algebraic data types in Haskell and concurrency in Go.