Microservices Architecture: practical implementations, benefits, and nuances
Korotenko, Anton (2024)
Korotenko, Anton
2024
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-202401101280
https://urn.fi/URN:NBN:fi:amk-202401101280
Tiivistelmä
The goal of the thesis was to conduct comprehensive research on the implementations, adoption, and evolution of microservices architecture, with a focus on C# and .NET frameworks. The study aims to help organizations and developers who are considering transitioning to microservices architecture.
The research methodologies included historical analysis, a comparative study, and an examination of realworld cases and generally accepted approaches. Moreover, the intention was to emphasize the benefits of
practically utilizing resources and ideas provided in the study.
As a result of this thesis, the architecture’s historical evolution was shown, explaining the reasons for different
changes. The case studies were analyzed, providing insightful typical failures and challenges in adopting a microservices architecture. A suitability table and an objectively created roadmap were provided, aiming to help
with organizations’ and developers’ decisions. The work can be taken as a skeleton for those who want to
adopt a microservices architecture.
The research methodologies included historical analysis, a comparative study, and an examination of realworld cases and generally accepted approaches. Moreover, the intention was to emphasize the benefits of
practically utilizing resources and ideas provided in the study.
As a result of this thesis, the architecture’s historical evolution was shown, explaining the reasons for different
changes. The case studies were analyzed, providing insightful typical failures and challenges in adopting a microservices architecture. A suitability table and an objectively created roadmap were provided, aiming to help
with organizations’ and developers’ decisions. The work can be taken as a skeleton for those who want to
adopt a microservices architecture.
