From df12fc6541db16d355a26fe6ba57b1f9b9749d54 Mon Sep 17 00:00:00 2001 From: Diogo Correia Date: Mon, 9 Sep 2024 12:35:01 +0200 Subject: [PATCH] week 3: diogogm-diogotc scientific paper proposal (#2399) --- .../week3/diogogm-diogotc/README.md | 42 +++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 contributions/scientific-paper/week3/diogogm-diogotc/README.md diff --git a/contributions/scientific-paper/week3/diogogm-diogotc/README.md b/contributions/scientific-paper/week3/diogogm-diogotc/README.md new file mode 100644 index 0000000000..187cb829b8 --- /dev/null +++ b/contributions/scientific-paper/week3/diogogm-diogotc/README.md @@ -0,0 +1,42 @@ +# Assignment Proposal + +## Title + +_Microservices: Architecting for Continuous Delivery and DevOps_ + +## Names and KTH ID + +- Diogo Melita (diogogm@kth.se) +- Diogo Correia (diogotc@kth.se) + +## Deadline + +Week 3 + +## Category + +Scientific paper + +## Description + +Paper: [DOI: 10.1109/ICSA.2018.00013](https://doi.org/10.1109/ICSA.2018.00013) - Available through the KTH Library + +The paper we intent to present summarizes experiences from Paddy Power about how +microservices architecture has been adopted in a Continuous Delivery context. +It highlights the substancial advantages of microservices - higher deployability, +modifiability, and better resilience - but also discusses the challenges introduced +by microservices - including the complexity of managing a larger number of services, +evolving service contracts, and handling the diversity of technologies. +To address this challenges, practical strategies are presented such as automated CD +pipelines and robust contract management. +The paper concludes by calling for further research in areas like managing service +interactions, refactoring service boundaries, and exploring alternative architectural +styles when microservices may not be suitable. + +**Relevance** + +Continuous deployment is a main topic of DevOps, but it is not always easy to implement +for every project. +Microservices, as presented in this paper, are an alternative to the common monolithic +approach that promises to solve roadblocks in the implementation of CD for software +projects.