Architectural design for resilience

Enterprise Information Systems

Volumn 4, Issue 2, 2010, Pages 137-152

  Liu, Dong ^a   Deters, Ralph ^a   Zhang, W J ^a  

^a UNIVERSITY OF SASKATCHEWAN   (Canada)

Author keywords

Fault tolerance; Redundancy; Reliability; Resilience; Self management; Service oriented architecture; Software architecture; Virtualisation

Indexed keywords

ARCHITECTURAL CONSTRAINTS; ARCHITECTURAL LEVELS; ARCHITECTURAL PROPERTIES; DESIGN DECISIONS; DISTRIBUTED COMPUTING; FAULT-TOLERANT SYSTEMS; NON-FUNCTIONAL REQUIREMENTS; RESILIENCE; SELF MANAGEMENT; STATE-OF-THE-ART TECHNOLOGY; VIRTUALISATION;

ARCHITECTURAL DESIGN; ARTS COMPUTING; DISTRIBUTED COMPUTER SYSTEMS; FAULT TOLERANCE; FAULT TOLERANT COMPUTER SYSTEMS; INFORMATION SERVICES; INFORMATION SYSTEMS; REDUNDANCY; SOFTWARE ARCHITECTURE; SOFTWARE RELIABILITY; THEOREM PROVING;

QUALITY ASSURANCE;

EID: 77951751212     PISSN: 17517575     EISSN: 17517583     Source Type: Journal    
DOI: 10.1080/17517570903067751     Document Type: Article

References (59)

1. Agha, G.A., 1985. ACTORS: A model of concurrent computation in distributed systems. Thesis (PhD). MIT.
2. Ahmed, A. and Hussain, S.S., 2007. Meta-model of resilient information system. Master's thesis. Blekinge Institute of Technology.
3. Alsberg, P.A. and Day, J.D., 1976. A principle for resilient sharing of distributed resources. In: ICSE'76: Proceedings of the 2nd international conference on Software engineering, San Francisco, California, United States. Los Alamitos, CA, USA: IEEE Computer Society Press, 562-570.
4. Anderson, C. and Bartholdi, J.J., 2000. Centralized versus decentralized control in manufacturing: Lessons from social insects. In: I.P. McCarthy and T. Rakotobe-Joel, eds. Complexity and Complex Systems in Industry, September. UK: The University of Warwick, 92-105.
5. Armbrust, M., et al., 2009. Above the clouds: A Berkeley view of cloud computing. Technical report UCB/EECS-2009-28, EECS Department, University of California, Berkeley.
6. Armstrong, J., 2003. Making reliable distributed systems in the presence of software errors. Thesis (PhD). The Royal Institute of Technology, Stockholm, Sweden.
7. Armstrong, J., 2007. Programming Erlang: Software for a Concurrent World. Raleigh, North Carolina: Pragmatic Bookshelf.
8. Berners-Lee, T., 1994. Universal Resource Identifiers in WWW. [online] http://tools.ietf.org/rfc/rfc1630.txt
9. Berners-Lee, T., Fielding, R., and Frystyk, H., 1996. Hypertext Transfer Protocol - HTTP/1.0. [online] http://tools.ietf.org/rfc/rfc1945.txt
10. Berners-Lee, T., Fielding, R., and Masinter, L., 2005. Uniform Resource Identifier (URI): Generic Syntax. [online] http://tools.ietf.org/rfc/rfc3986.txt
11. Bondi, A.B., 2000. Characteristics of scalability and their impact on performance. In: WOSP'00: Proceedings of the 2nd international workshop on Software and performance, Ottawa, Ontario, Canada. New York, NY, USA: ACM Press, 195-203.
12. Booch, G., et al., 2007. Object-Oriented Analysis and Design with Applications, 3rd ed. Redwood City, CA, USA: Addison-Wesley Professional.
13. Box, D., 2004. Code Name Indigo: A Guide to Developing and Running Connected Systems with Indigo. MSDN Magazine. http://msdn.microsoft.com/msdnmag/issues/04/01/indigo/default.aspx
14. Brewer, E.A., 2000. Towards robust distributed systems (abstract). In: PODC'00: Proceedings of the nineteenth annual ACM symposium on Principles of distributed computing, Portland, Oregon, United States. New York, NY, USA: ACM, p. 7.
15. Cavano, J.P. and McCall, J.A., 1978. A framework for the measurement of software quality. In: Proceedings of the software quality assurance workshop on Functional and performance issues, ACM Press, 133-139.
16. Chang, F., et al., 2006. Bigtable: a distributed storage system for structured data. In: OSDI'06: Proceedings of the 7th symposium on Operating systems design and implementation, Seattle, Washington Berkeley, CA, USA: USENIX Association, 205-218.
17. Chen, L. and Avizienis, A., 1995. N-version programming: A fault-tolerance approach to reliability of software operatlon. In: Twenty-Fifth International Symposium on Fault-Tolerant Computing, June, 1995, 'Highlights from Twenty-Five Years', June, 113-119.
18. Coulouris, G., Dollimore, J., and Kindberg, T., 2005. Distributed Systems: Concepts and Design, 4th ed. fourth Redwood City, CA, USA: Addison Wesley.
19. Dan, A., et al., 2004. Web services on demand: WSLA-driven automated management. IBM Systems Journal, Special Issue on Utility Computing, 43 (1), 136-158.
20. DeCandia, G., et al., 2007. Dynamo: amazon's highly available key-value store. In: SOSP'07: Proceedings of twenty-first ACM SIGOPS symposium on Operating systems principles, Stevenson, Washington, USA. New York, NY, USA: ACM, 205-220.
21. Di Marzo Serugendo, G., et al., 2007. A metadata-based architectural model for dynamically resilient systems. In: SAC'07: Proceedings of the 2007 ACM symposium on Applied computing, Seoul, Korea. New York, NY, USA: ACM, 566-572.
22. Erenkrantz, J.R., et al., 2007. From representations to computations: the evolution of web architectures. In: ESEC-FSE'07: Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering, Dubrovnik, Croatia. New York, NY, USA: ACM, 255-264.
23. Estefan, J.A., et al., 2008. Reference Model for Service Oriented Architecture V 1.0. [online] http://www.oasis-open.org/committees/download.php/19679/soa-rm-cs.pdf
24. Fielding, R., et al., 1999. Hypertext Transfer Protocol - HTTP/1.1. [online] http://www.ietf.org/rfc/rfc2616.txt
25. Fielding, R.T., 2000. Architectural styles and the design of network-based software architectures. Thesis (PhD). University of California, Irvine.
26. Fielding, R.T. and Taylor, R.N., 2002. Principled design of the modern Web architecture. ACM Transactions on Internet Technology, 2 (2), 115-150.
27. Gilbert, S. and Lynch, N., 2002. Brewer's conjecture and the feasibility of consistent, available, partition-tolerant web services. SIGACT News, 33 (2), 51-59.
28. Gray, J., 1981. The transaction concept: virtues and limitations (invited paper). In: VLDB'1981: Proceedings of the seventh international conference on Very Large Data Bases, Cannes, France VLDB Endowment, 144-154.
29. Greschler, D. and Mangan, T., 2002. Networking lessons in delivering 'Software as a Service'-part I. International Journal of Network Management, 12 (5), 317-321.
30. Gross, D. and Yu, E., 2001. From non-functional requirements to design through patterns. Requirements Engineering, 6 (1), 18-36.
31. Haerder, T. and Reuter, A., 1983. Principles of transaction-oriented database recovery. ACM Computing Surveys, 15 (4), 287-317.
32. Hariri, S. and Parashar, M., 2004. Tools and Environments for Parallel and Distributed Computing. Somerset, NJ: Wiley-Interscience.
33. Hewitt, C., Bishop, P., and Steiger, R., 1973. A universal modular ACTOR formalism for artificial intelligence. In: IJCAI, 235-245.
34. Hill, M.D., 1990. What is scalability? ACM SIGARCH Computer Architecture News, 18 (4), 18-21.
35. IBM, An Architectural Blueprint for Autonomic Computing, 2003. Technical report http://www.ibm.com/developerworks/autonomic/library/ac-summary/ac-blue.html.
36. Kaye, D., 2003. Loosely Coupled: The Missing Pieces of Web Services. Marin County, Calif: RDS Press.
37. Kephart, J.O. and Chess, D.M., 2003. The vision of autonomic computing. IEEE Computer, 36(1),41-50.
38. Knight, J.C. and Lev, N.G., 1986. An experimental evaluation of the assumption of independence in multiversion programming. IEEE Transactions on Software Engineering, 12,96-109.
39. Kruchten, P., 1995. Architectural blueprints-The '4+1' view model of software architecture. IEEE Software, 12 (6), 42-50.
40. Luke, E., 1993. Defining and measuring scalability. In: Proceedings of the Scalable Parallel Libraries Conference, 1993. IEEE, 183-186.
41. Padhye, J., et al., 1998. Modeling TCP throughput: a simple model and its empirical validation. In: SIGCOMM'98: Proceedings of the ACM SIGCOMM'98 conference on Applications, technologies, architectures, and protocols for computer communication, Vancouver, British Columbia, Canada. New York, NY, USA: ACM, 303-314.
42. Page-Jones, M., 1988. The practical guide to structured systems design, 2nd ed. Englewood Cliffs, NJ: Yourdon Press.
43. Perry, D.E. and Wolf, A.L., 1992. Foundations for the study of software architecture. SIGSOFT Softw. Eng. Notes, 17 (4), 40-52.
44. Pressman, R.,2004. Software Engineering: A Practitioner's Approach,6th ed. Ontario, Canada: McGraw-Hill Higher Education.
45. Richardson, L. and Ruby, S., 2007. RESTful Web Services. Sebestopal, CA: O'Reilly.
46. Robertson, S. and Robertson, J., 2006. Mastering the Requirements Process, 2nd ed. Redwood City, CA, USA: Addison Wesley Professional.
47. Sahai, A., Durante, A., and Machiraju, V., 2001. Towards Automated SLA Management for Web Services. Technical report, HP Laboratories Palo Alto http://www.hpl.hp.com/techreports/2001/HPL-2001-310R1.pdf
48. Schneirla, T.C., 1971. Army Ants. A Study in Social Organization. San Francisco: W.H. Freeman & Co.
49. Shooman, M.L., 2002. Reliability of Computer Systems and Networks: Fault Tolerance, Analysis, and Design. Malden, MA: Wiley-Interscience.
50. Siemwiorek, D., 1991. Architecture of fault-tolerant computers: an historical perspective. Proceedings of the IEEE, 79 (12), 1710-1734.
51. Stonebraker, M. and Cetintemel, U., 2005. "One size fits all": An idea whose time has come and gone. In: ICDE'05: Proceedings of the 21st International Conference on Data Engineering. Washington, DC, USA: IEEE Computer Society, 2-11.
52. Tosic, V., Lutfiyya, H., and Tang, Y., 2006. Extending Web Service Offerings Infrastructure (WSOI) for management of mobile/embedded XML web services. In: The 8th IEEE International Conference on and Enterprise Computing, E-Commerce, and E-Services, The 3rd IEEE International Conference on E-Commerce Technology, 87-94.
53. Vinoski, S., 2008a. Convenience over correctness. IEEE Internet Computing, 12 (4), 89-92.
54. Vinoski, S., 2008b. Serendipitous reuse. IEEE Internet Computing, 12 (1), 84-87.
55. Vogels, W., 2009. Eventually consistent. Commun. ACM, 52 (1), 40-44.
56. Waldo, J., et al., 1994. A Note on Distributed Computing. Technical report, Sun Microsystems Laboratories http://research.sun.com/techrep/1994/smli_tr-94-29.pdf
57. Walker, B., et al., 2004. Resilience, adaptability and transformability in social-ecological systems. Ecology and Society, 9, 5.
58. Wang, G., et al., 2004. Integrated quality of service (QoS) management in service-oriented enterprise architectures. In: EDOC 2004: Proceedings of Eighth IEEE International Enterprise Distributed Object Computing Conference, 21-32.
59. Weiss, A., 2007. Computing in the clouds. netWorker, 11 (4), 16-25.