-
Notifications
You must be signed in to change notification settings - Fork 428
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
week 3: diogogm-diogotc scientific paper proposal
- Loading branch information
1 parent
0e623cc
commit 2f6bba7
Showing
1 changed file
with
42 additions
and
0 deletions.
There are no files selected for viewing
42 changes: 42 additions & 0 deletions
42
contributions/scientific-paper/week3/diogogm-diogotc/README.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
# Assignment Proposal | ||
|
||
## Title | ||
|
||
_Microservices: Architecting for Continuous Delivery and DevOps_ | ||
|
||
## Names and KTH ID | ||
|
||
- Diogo Melita ([email protected]) | ||
- Diogo Correia ([email protected]) | ||
|
||
## 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. |