ings of the 10th IEEE Symposium on Computers and Communication (ISCC 2005) (pp. 927- 932). IEEE. June 27-30, 2005, Cartagena, Murcua, Spain. Hoff, T. 2015. The Stunning Scale of AWS and What It Means for the Future of the Cloud. http://highscalabil- ity.com/blog/2015/1/12/the-stunning-scale-of-aws-and-what-it-means-for-the-future-o.html Martersteck, K. E. and Spencer, A. E. Jr. 1985. The 5ESS switching system-Introduction. AT&T Technical Journal, 64(6), part 2, 1305-1314. IEEE Computer Society. 2010. IEEE Std. 1044-2099 (Revisions of IEEE Std. 1044-1993) IEEE Standard Classification for Software Anomalies. New York: IEEE Computer Society. Johnson, C. R. et al. 2004. VoIP reliability: A service provider's perspective. IEEE Communications, July, pp. 48-54. Klincewicz, J. G. 2013. Designing an IP link topology for a metro area backbone network. International Journal of Interdisciplinary Telecommunications and Networking, 5(1), 26-42. Krishnan, K. D. 1994. Unified models of survivability for multi-technology networks. In Proceedings of ITC 14. New York: Elsevier Science B.V, Volume 1A, pp. 655-665. Lancaster, W. G. 1986. Carrier grade: Five nines, the myth and the reality. Pipeline (www.pipelinepub.com), 3(11), 6. Lyu, M. R. 1996. Handbook of Software Reliability Engineering. Los Alamitos, CA: IEEE Computer Society Press and McGraw-Hill. Martersteck, K. E. 1981. The 4ESS system evolution. Bell System Technical Journal, 60(6), part 2, 1041-1228. Metz, C. 2002. IP anycast: Point-to-(any) point communication. IEEE Internet Computing, 6(2), 94-98. Miller, R. 2015. Inside Amazon's Cloud Computing Infrastructure. http://datacenterfrontier.com/ inside-amazon-cloud-computing-infrastructure/ Musa, J. 1999. Software Reliability Engineering. New York: McGraw-Hill. Rackspace. 2015. Creating Resilient Architectures on Microsoft Azure. Windcrest, TX: Rackspace. Ramesh Govindan (Google, USC); Ina Minei, Mahesh Kallahalla, Bikash Koley, Amin Vahdat (Google). 2016. Evolve or die: High availability design principles drawn from Google'