Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Reducing Friction in Cloud Migration of Services
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering. Ericsson AB.ORCID iD: 0000-0001-9898-2222
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0003-1350-7030
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0003-3567-9300
(English)Manuscript (preprint) (Other academic)
Abstract [en]

Public cloud services are integral to modern software development, oeringscalability and exibility to organizations.Based on customer requests, alarge product development organization considered migrating the microservice-based product deployments of a large customer to a public cloud provider.

We conducted an exploratory single-case study, utilizing quantitative andqualitative data analysis to understand how and why deployment costs wouldchange when transitioning the product from a private to a public cloud en-vironment while preserving the software architecture. We also isolated themajor factors driving the changes in deployment costs.

We found that switching to the customer-chosen public cloud providerwould increase costs by up to 50%, even when sharing some resources be-tween deployments, and limiting the use of expensive cloud services such assecurity log analyzers. A large part of the cost was related to the sizing andlicense costs of the existing relational database, which was running on Vir-tual Machines in the cloud. We also found that existing system integrators,using the product via its API, were likely to use the product ineciently, inmany cases causing at least 10% more load to the system than needed.

From a deployment cost perspective, successful migration to a publiccloud requires considering the entire system architecture, including serviceslike relational databases, value-added cloud services, and enabled productfeatures. Our study highlights the importance of leveraging end-to-end us-age data to assess and manage these cost drivers eectively, especially inenvironments with elastic costs, such as public cloud deployments.

National Category
Software Engineering
Research subject
Software Engineering
Identifiers
URN: urn:nbn:se:bth-28613OAI: oai:DiVA.org:bth-28613DiVA, id: diva2:1997626
Part of project
SERT- Software Engineering ReThought, Knowledge FoundationAvailable from: 2025-09-12 Created: 2025-09-12 Last updated: 2025-10-17Bibliographically approved
In thesis
1. On Quantifying Software Craftsmanship Concepts
Open this publication in new window or tab >>On Quantifying Software Craftsmanship Concepts
2025 (English)Doctoral thesis, comprehensive summary (Other academic)
Abstract [en]

Background: Books on software craftsmanship typically focus on small teams or individual behavior, and are seldom associated with large, globally distributed organizations that develop and maintain long-lived software systems.

Objective: This thesis aims to quantify the effects of systematically derived aspects of software craftsmanship in industrial settings involving large-scale organizations, with developers spread around the globe.

Method: We employ mixed-methods studies, utilizing both qualitative and quantitative data collection and analysis. A Systematic Literature Review (SLR), together with a longitudinal industrial case study, is used to derive an initial anatomy of software craftsmanship, and we use case studies, experience reports and action research to explore and quantify aspects of this anatomy. We use Bayesian methods to analyze data obtained via archival analysis, as well as Likert-scale data obtained froma survey using the Technology Adoption Model (TAM). Qualitative data has been analyzed using thematic coding, and we use focus groups to validate our conclusions with the studied subjects.

Results: Based on the SLR results and a industrial case study, we derive an anatomy of software craftsmanship, based on four themes, 17 principles and 47 practices. The effects of some practices from this anatomy are then quantified in subsequent articles in the thesis.

Conclusion: Based on literature and case study results, we have found a usable conceptual map of software craftsmanship. However, it remains to be seen how this map will stay relevant, in the face of how cloud migrations and AI-powered Large-Language Model tools will impact future software engineers.

Place, publisher, year, edition, pages
Karlskrona: Blekinge Tekniska Högskola, 2025. p. 217
Series
Blekinge Institute of Technology Doctoral Dissertation Series, ISSN 1653-2090 ; 2025:12
Keywords
Software Craftsmanship, Professionalism, Large-scale software development
National Category
Software Engineering
Research subject
Software Engineering
Identifiers
urn:nbn:se:bth-28614 (URN)978-91-7295-512-7 (ISBN)
Public defence
2025-11-28, J1630, BTH, Valhallavägen 1, Karlskrona, 09:00 (English)
Opponent
Supervisors
Available from: 2025-10-20 Created: 2025-09-12 Last updated: 2025-11-06Bibliographically approved

Open Access in DiVA

No full text in DiVA

Authority records

Sundelin, AndersGonzalez-Huerta, JavierWnuk, Krzysztof

Search in DiVA

By author/editor
Sundelin, AndersGonzalez-Huerta, JavierWnuk, Krzysztof
By organisation
Department of Software Engineering
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar

urn-nbn

Altmetric score

urn-nbn
Total: 30 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf