2015/07/29 by Armin Balalaie, Abbas Heydarnoori, Balalaie, Armin +3 · 1 citation
Computer Science · #Architectural style #Architecture #Cloud Computing and Resource Management #Cloud computing #Computer science #Computer security #Context (archaeology) #Database #Distributed #Distributed computing #Exploit #FOS: Computer and information sciences #Flexibility (engineering) #IoT and Edge/Fog Computing #Microservices #Operating system #Parallel #Premise #Scalability #Software Engineering (cs.SE) #Software System Performance and Reliability #Software portability #and Cluster Computing (cs.DC) #cs.DC #cs.SE
paper · pdf · doi:10.48550/arxiv.1507.08217
published in arXiv (Cornell University) (Cornell University)
arxiv created 2015/07/29 · openalex publication_date 2015/07/29 · arxiv updated 2015/07/30 · openalex created_date 2025/10/10 · openalex updated_date 2026/07/28
Migration to the cloud has been a popular topic in industry and academia in\nrecent years. Despite many benefits that the cloud presents, such as high\navailability and scalability, most of the on-premise application architectures\nare not ready to fully exploit the benefits of this environment, and adapting\nthem to this environment is a non-trivial task. Microservices have appeared\nrecently as novel architectural styles that are native to the cloud. These\ncloud-native architectures can facilitate migrating on-premise architectures to\nfully benefit from the cloud environments because non-functional attributes,\nlike scalability, are inherent in this style. The existing approaches on cloud\nmigration does not mostly consider cloud-native architectures as their\nfirst-class citizens. As a result, the final product may not meet its primary\ndrivers for migration. In this paper, we intend to report our experience and\nlessons learned in an ongoing project on migrating a monolithic on-premise\nsoftware architecture to microservices. We concluded that microservices is not\na one-fit-all solution as it introduces new complexities to the system, and\nmany factors, such as distribution complexities, should be considered before\nadopting this style. However, if adopted in a context that needs high\nflexibility in terms of scalability and availability, it can deliver its\npromised benefits.\n