The Seven Rules of Highly Successful (Cloud) Services
So you've got a cloud-based service. Good for you! I bet its brilliant, is brilliantly fault-tolerant 'cos of Erlang/OTP, and is going to make you Pots o' Money! That is, of course, assuming that you have prepared yourself for the inevitable "Oh S**t!" moment, when It Goes Down. Herewith a couple of pointers to help you prepare for everything not working exactly the way it is supposed to (Servers die? really?)… 1) Make sure that you understand your entire system . Done? Good, now make sure that all of your developers understand the entire system. Specialization might be good (and don't get me wrong, weed-whackers are *very* useful little tools, especially when you get into the weeds :-) ), but if they don't grok the big picture, well, you're hosed. Capturing vast quantities of scoring data could be really useful for GUI updates, and might be easy to implement from an API perspective, but if your persistence layer...