2023
DOI: 10.1016/j.jss.2023.111702
|View full text |Cite
|
Sign up to set email alerts
|

Legacy systems to cloud migration: A review from the architectural perspective

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

2023
2023
2024
2024

Publication Types

Select...
2
2
1
1

Relationship

1
5

Authors

Journals

citations
Cited by 7 publications
(5 citation statements)
references
References 30 publications
0
5
0
Order By: Relevance
“…The Lift-and-Shift approach, for example, only involves taking existing as-is on-premise applications and moving them to the cloud as a separate service while preserving existing architecture and limiting the cloud scalability features (Kalia et al, 2020). Thus, decomposing the monolith application into a suitable service boundary is crucial when migrating to the distributed cloud architecture (Hasan et Yadav et al, 2020) were introduced in assisting the decomposition process, not all the migration strategies consider quality assurance in their outline, hence introducing post-migration quality concerns consisting of maintainability, performance, security, and reliability (Hasan et al, 2023b). To overcome these gaps, we undertook a shift-left approach in proposing a decomposition framework to ensure the migration to the cloud achieved its goals, thus ful lling cloud-native bene ts (Fehling et al, 2014) at the earliest migration stage.…”
Section: The Decomposition Frameworkmentioning
confidence: 99%
See 3 more Smart Citations
“…The Lift-and-Shift approach, for example, only involves taking existing as-is on-premise applications and moving them to the cloud as a separate service while preserving existing architecture and limiting the cloud scalability features (Kalia et al, 2020). Thus, decomposing the monolith application into a suitable service boundary is crucial when migrating to the distributed cloud architecture (Hasan et Yadav et al, 2020) were introduced in assisting the decomposition process, not all the migration strategies consider quality assurance in their outline, hence introducing post-migration quality concerns consisting of maintainability, performance, security, and reliability (Hasan et al, 2023b). To overcome these gaps, we undertook a shift-left approach in proposing a decomposition framework to ensure the migration to the cloud achieved its goals, thus ful lling cloud-native bene ts (Fehling et al, 2014) at the earliest migration stage.…”
Section: The Decomposition Frameworkmentioning
confidence: 99%
“…The relevant quality attribute is known as maintainability -where the degree of effectiveness and e ciency of an application can be changed, modi ed, or corrected to meet requirements (ISO/IEC, 2010). Despite of various decomposition techniques proposed from different perspectives, such as business functionality, domain-driven, and process mining, none of the mentioned approaches focuses on the maintainer's or developer's perspective, resulting in the migrated application did not achieve migration objective and thus obtaining maintainability concern after the migration (Hasan et al, 2023b). Therefore, it is essential to ensure that decomposed applications must be maintainable by developers to avoid post-migration accumulated waste and technical debt (Fan & Ma, 2017;Lenarduzzi et al, 2020;Taibi et al, 2017).…”
Section: Overviewmentioning
confidence: 99%
See 2 more Smart Citations
“…Software errors can stem devastating effects to financial loss, time delays, or even risks to life [13], [14]. Numerous frameworks for migrating from monolith to cloud have been introduced [1], [15]- [18], yet they still do not adequately address quality considerations after the migration [19]. Therefore, the migration did not accomplish its objective [5], thus introducing new product quality challenges such as application maintainability, security, reliability, and compatibility [8], [20].…”
Section: Introductionmentioning
confidence: 99%