Cited by 735Software System Performance and ReliabilitySoftware Engineering Techniques and PracticesAdvanced Software Engineering Methodologies

Microservices Architecture Enables DevOps: Migration to a Cloud-Native Architecture

Balalaie, Armin, Heydarnoori, Abbas, Jamshidi, Pooyan·2016·IEEE Software

Abstract

This article reports on experiences and lessons learned during incremental migration and architectural refactoring of a commercial mobile back end as a service to microservices architecture. It explains how the researchers adopted DevOps and how this facilitated a smooth migration.

Integrity signals

Registry

Crossref · 10.1109/ms.2016.64

Cites

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Cited by

Sorted by citations

Authors
Balalaie, A., Heydarnoori, A., & Jamshidi, P.
Affiliations
  • Sharif University of Technology (IR)
  • Imperial College London (GB)
Venue
IEEE Software
Published
2016-05
Volume
33
Issue
3
Pages
42-52
ISSN
  • 0740-7459 (ISSN-L)
  • 1937-4194
OpenAlex
W2322013807
Cited by
735
References
0
Citations by year
2026: 31 · 2025: 51 · 2024: 80 · 2023: 71 · 2022: 84 · 2021: 102 · 2020: 91 · 2019: 94 · 2018: 82 · 2017: 35 · 2016: 14
FWCI
70.56
Type
journal article
Language
en
Open access
closed
Locations
  • IEEE Software (publishedVersion)
  • Spiral (Imperial College London) (submittedVersion)
Topics
  • Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Artificial Intelligence › Advanced Software Engineering Methodologies
Keywords
microservices, DevOps, cloud-native architecture, architectural refactoring, incremental migration, lessons learned

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review