Microservices: Architecting for Continuous Delivery and DevOps
The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
Businesses today need to respond to customer needs at unprecedented speeds. Driven by this need for speed, many companies are rushing to the DevOps movement and implementing Continuous Delivery (CD). I had been implementing DevOps and CD for Paddy Power, a multi-billion-euro betting and gaming company, for four years. I had found that software architecture can be a key barrier. To address the architectural challenges, we tried an emerging architectural style called Microservices. I have observed increased deployability, modifiability, and resilience to design erosion. At the same time, I also observed new challenges associated with the increased number of services, evolving contracts among services, technology diversity, and testing. I share the practical strategies that can be employed to address these new challenges, discuss situations for which Microservices may not be a good choice, and outline areas that require further research.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Microservices Architecture Enables DevOps: Migration to a Cloud-Native Architecture
Balalaie, A., Heydarnoori, A., & Jamshidi, P. (2016) · IEEE Software · doi:10.1109/ms.2016.64 · Cited by 735 · cited 1×
“Balalaie, et al. [16] reported their experiences when migrating to Microservices.”
Background
Cited by
Kim, H., Choi, H., Kang, H., An, J., Yeom, S., & Hong, T. (2021) · Renewable and Sustainable Energy Reviews · doi:10.1016/j.rser.2021.110755 · Cited by 367
Gu, S., Rong, G., Ren, T., Zhang, H., Shen, H., Yu, Y., Li, X., Ouyang, J., & Chen, C. (2023) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2023.3241299 · Cited by 46
“En-ablingcontinuousdeliveryoffeaturesmotivatesthearchitecturalmigrationfromthemonolithictothemicroservices[31].”
Understanding software architecture erosion: A systematic mapping study
Li, R., Liang, P., Soliman, M., & Avgeriou, P. (2022) · Journal of Software: Evolution and Process · doi:10.1002/smr.2423 · Cited by 45
Metadata
- Authors
- Chen, L.
- Venue
- 2018 IEEE International Conference on Software Architecture (ICSA)
- Publisher
- IEEE
- Published
- 2018-04
- Pages
- 39-397
- OpenAlex
- W2884367066
- Cited by
- 152
- References
- 1
- FWCI
- 16.71
- Type
- conference paper
- Language
- en
- Open access
- closed
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
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.