Page 29 - 《软件学报》2021年第5期
P. 29

殷康璘 等:基于混沌工程的微服务韧性风险识别和分析                                                       1253


                [16]    Holling CS. Resilience and stability of ecological systems. Annual Review of Ecology and Systematics, 1973,4(1):1−23. [doi: 10.
                     1146/annurev.es.04.110173.000245]
                [17]    Hosseini S, Barker K, Ramirez-Marquez JE. A review of definitions and measures of system resilience. Reliability Engineering &
                     System Safety, 2016,145(2016):47−61. [doi: 10.1016/j.ress.2015.08.006]
                [18]    Xue X, Wang L, Yang RJ. Exploring the science of resilience: Critical review and bibliometric analysis. Natural Hazards, 2018,
                     90(1):477−510. [doi: 10.1007/s11069-017-3040-y]
                [19]    Laprie JC. Dependability: Basic Concepts and Terminology. Vienna: Springer-Verlag, 1992. [doi: 10.1007/978-3-7091-9170-5]
                [20]    Laprie JC. From dependability to resilience. In: Proc. of the 38th IEEE/IFIP Int’l Conf. on Dependable Systems and Networks. Los
                     Alamitos: IEEE Computer Society, 2008. G8−G9.
                [21]    Wolter K, Avritzer A, Vieira M, Van Moorsel A, eds. Resilience Assessment and Evaluation of Computing  Systems. Berlin,
                     London: Springer-Verlag, 2012. [doi: 10.1007/978-3-642-29032-9]
                [22]    Trivedi KS, Kim DS, Ghosh R. Resilience in computer systems and networks. In: Proc. of the 2009 Int’l Conf. on Computer-aided
                     Design. New York: ACM, 2009. 74−77. [doi: 10.1145/1687399.1687415]
                [23]    Bishop M, Carvalho M, Ford R, et al. Resilience is more than availability. In: Proc. of the 2011 New Security Paradigms Workshop.
                     New York: ACM, 2011. 95−104. [doi: 10.1145/2073276.2073286]
                [24]    Diez O,  Silva A. Resilience  of  cloud computing  in critical  systems. Quality and  Reliability Engineering  Int’l,
                     2014,30(3):397−412. [doi: 10.1002/qre.1579]
                [25]    Wolff E. Microservices: Flexible Software Architecture. Boston: Addison-Wesley Professional, 2016.
                [26]    Toffetti G, Brunner S, Blöchlinger M, et al. An architecture for self-managing microservices. In: Proc. of the 1st Int’l Workshop on
                     Automated Incident Management in Cloud. New York: ACM, 2015. 19−24. [doi: 10.1145/2747470.2747474]
                [27]    Rusek M, Dwornicki G, Orłowski A. A decentralized system for load balancing of containerized microservices in the cloud. In:
                     Proc. of the Int’l Conf. on Systems Science. Cham: Springer-Verlag, 2016. 142−152. [doi: 10.1007/978-3-319-48944-5_14]
                [28]    Soenen T, Tavernier W, Colle D, et al. Optimising microservice-based reliable NFV management & orchestration architectures. In:
                     Proc. of the 2017 9th Int’l Workshop on Resilient Networks Design and Modeling (RNDM). Piscataway: IEEE, 2017. 1−7. [doi:
                     10.1109/RNDM.2017.8093034]
                [29]    Haselböck S, Weinreich R, Buchgeher G. Decision guidance models for microservices: Service discovery and fault tolerance. In:
                     Proc. of the 5th European Conf. on  the  Engineering of Computer-based  Systems.  New  York:  ACM, 2017. 1−10. [doi: 10.1145/
                     3123779.3123804]
                [30]    Heorhiadi V, Rajagopalan S, Jamjoom H, et al. Gremlin: Systematic resilience testing of microservices. In: Proc. of the 2016 IEEE
                     36th Int’l Conf. on Distributed Computing Systems (ICDCS). Piscataway: IEEE, 2016. 57−66. [doi: 10.1109/ICDCS.2016.11]
                [31]    Düllmann TF, van Hoorn A. Model-driven generation of microservice architectures for benchmarking performance and resilience
                     engineering approaches. In: Proc. of the 8th ACM/SPEC on Int’l Conf. on Performance Engineering Companion. New York: ACM,
                     2017. 171−172. [doi: 10.1145/3053600.3053627]
                [32]    Giedrimas V, Omanovic S, Alic D. The aspect of resilience in microservices-based software design. In: Proc. of the Federation of
                     Int’l Conf. on Software Technologies: Applications and Foundations. Cham: Springer-Verlag, 2018. 589−595. [doi: 10.1007/978-3-
                     030-04771-9_44]
                [33]    Van Hoorn A, Aleti A, Düllmann TF, et al. ORCAS: Efficient resilience benchmarking of microservice architectures. In: Proc. of
                     the 2018 IEEE Int’l Symp. on Software Reliability Engineering Workshops (ISSREW). Piscataway: IEEE, 2018. 146−147. [doi: 10.
                     1109/ISSREW.2018.00-10]
                [34]    Jagiełło M, Rusek  M, Karwowski W.  Performance and  resilience  to  failures  of an cloud-based application:  Monolithic and
                     microservices-based  architectures  compared.  In: Proc.  of the IFIP Int’l  Conf. on Computer Information Systems  and Industrial
                     Management. Cham: Springer-Verlag, 2019. 445−456. [doi: 10.1007/978-3-030-28957-7_37]
                [35]    Williams RC, Pandelios GJ, Behrens SG. Software risk evaluation (SRE) method description: Version 2.0. Pittsburgh: Software
                     Engineering Institute, Carnegie Mellon University, 1999.
                [36]    Lee WS, Grosh DL, Tillman FA, et al. Fault tree analysis, methods, and applications—A review. IEEE Trans. on Reliability, 1985,
                     34(3):194−203. [doi: 10.1109/TR.1985.5222114]
                [37]    Alexander I. Misuse cases: Use cases with hostile intent. IEEE Software, 2003,20(1):58−66. [doi: 10.1109/MS.2003.1159030]
   24   25   26   27   28   29   30   31   32   33   34