Systematic scalability analysis for microservices granularity adaptation design decisions

Abstract

Microservices have gained wide recognition and acceptance in software industries as an emerging architectural style for autonomous, scalable, and more reliable computing. A critical problem related to microservices is reasoning about the suitable granularity level of a microservice (i.e. when and how to merge or decompose microservices). Although scalability is pronounced as one of the major factors for adoption of microservices, there is a general gap of approaches that systematically analyse the dimensions and metrics which are important for scalability-aware granularity adaptation decisions. To the best of our knowledge, the stateof-art in reasoning about microservice granularity adaptation is neither: 1) driven by microservice-specific scalability dimensions and metrics nor, 2) follow systematic scalability analysis to make scalability-aware adaptation decisions. In this paper, we address the aforementioned problems using a two-fold contribution.Firstly, we contribute to a working catalogue of microservice-specific scalability dimensions and metrics.Secondly, we describe a novel application of scalability goal-obstacle analysis for the context of reasoning about microservice granularity adaptation. We analyse both contributions by comparing their usage on a hypothetical microservice architecture against ad-hoc scalability assessment for the same architecture. This analysis shows how both contributions can aid making scalability-aware granularity adaptation decisions.

A systematic mapping study: The new age of software architecture from monolithic to microservice architecture—awareness and challenges

“…System migration to microservice optimizes software architecture decentralization, replaceability, traceability, and autonomy. Although researchers are not persuaded by any clear concept of microservice, they are modeling techniques and their characteristics [21]. The main drawback of the existing monolithic systems is their lack of scalability when performing a certain service task [6].…”

“…MSA is an architectural style for software development as a suite of self‐deployable services. Microservices are small modules and lightweight mechanism which runs as a unique process and automated deployment [21]. Microservices can be written in different programming languages, and they can use different database technologies.…”

Identification of monolith functionality refactorings for microservices migration

“…The approaches on service identification and on service granularity built on top of microservices quality metrics, such as cohesion, coupling and complexity, 24 or scalability. 25 This paper builds on previous work, Almeida and Silva, 11 that proposes two metrics to measure the complexity associated with the functionality migration to SAGAs pattern in a microservices architecture and the complexity that this implementation adds to the implementation of other functionalities. These metrics are built on the number of intermediate states and the number of inter-microservice invocations associated with the functionality implementation.…”

Research on multi-dimensional reconstruction mechanism of cloud native full link in the Metaverse scenario

“…In terms of architecture, the Microservices architecture is an improvement based on SOA architecture, and incorporates the idea of componentization and domain modeling. First, the system is divided into multiple Microservices, which are deployed independently in a Loose coupling manner; Secondly, each Microservices only needs to complete its own tasks with high quality, and each task represents a ne-grained business capability; As a result, various businesses have been completely componentized and service-oriented [9][10][11][12]; Finally, modules that provide domain service capabilities realize service composition and assembly in the underlying Microservices architecture. As shown in Fig.…”