Using Microservice Architecture for High-Load Information Systems on the Example of MedicinePlanner Service

Abstract

Nowadays, the topic of health is very relevant, and taking pills is one of the ways to stay healthy. So, there is a problem of a timely pill taking and it is important to develop a reminder system for taking medicine, available to the user anytime and anywhere. Moreover, to develop a fault-tolerant high-load system it is necessary to use modern design patterns to improve the scalability and maintenance of the software product. The article substantiates the importance of using one of the possible approaches to designing servers for highly loaded information systems – microservice architecture, in particular on the example of our own software product – MedicinePlanner, which supports further scalability through the implementation of the abovementioned architecture on the server side. This research presents the description of software development process on the basis of microservice architecture, using widely spread frameworks and tools, among which are.NET and gRPC. The client side has been built with a modular structure using Angular, containerization of all entities and system modules has been done, and support for automatic deployment in Azure has been added. In addition, containerization and deployment processes have been considered, as they are the integral part of the full development cycle. Among the main results of this study are the conducted analysis of the architecture of client and server parts of the application, description of the used design patterns and usage of microservice architecture. In contrast to monolithic architecture, microservice architecture solves one of the problems of this study – scalability of applications, the solution to which has been described in this work. Moreover, it is isolated from errors, so even in the event of any malfunctions, the failure of the entire system is impossible due to the allocation of resources and business logic. Finally, the comparative analysis of microservice and monolithic architecture has been carried out, taking into consideration such important factors as time spent on development, the amount of changed code during the process of developing new features, which has demonstrated that microservice architecture saves 30% of development time.