Browsing by Author "Kalske, Miika"

Monolithic architecture has been the standard way to architect applications for years. Monolithic applications use a single codebase which makes the deploying and development easier without adding any additional complexity as long as the size of the application stays relatively small. When the size of the codebase grows the architecture might deteriorate. This slows down the development and making it harder to on-board new developers. Microservice architecture is a novel architecture style that tries to solve these issues in larger codebases. Microservice architecture consists of multiple small autonomous services that are deployed and developed separately. Microservice architecture enables more fine-grained scaling and makes it possible to have faster development cycles by decreasing the amount of regression testing that is needed, because each of the services can be deployed and updated separately from each other. Microservice architecture provides also multiple new challenges that have to be solved in order to get the benefit from them. These challenges are such as the handling of distributed transactions, communication between microservices, separation of concerns in microservices and so on. On top of the technical challenges there are also organizational and operational challenges. The operational challenges are such as monitoring, logging and automated deployment of microservices. This thesis studies the differences between monolithic and microservice architecture and pinpoints the main challenges on the transition from monolithic architecture to microservice architecture. A proof of concept on how to transform a single bounded context from monolith to microservices will be made to get a better understanding of the challenges. Also a plan how to migrate tangled bounded contexts from monolith to microservices will be made in order to fully support the transition process in the future. The results from the proof of concept and the plan that was made show that the cohesion and loose coupling is more likely to stay when the bounded context is transformed to microservice.