A pattern language for scalable microservices-based systems

Márquez, Gastón; Villegas, Mónica M.; Astudillo, Hernán

doi:10.1145/3241403.3241429

Cited by 12 publications

(4 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…A Computac ¸ão em Nuvem foi estabelecida ao longo dos anos como um padrão de fato para a execuc ¸ão de aplicac ¸ões devido à sua capacidade de provisionar recursos sob demanda pela Internet [Liu et al 2012]. Embora o provisionamento de recursos em ambientes de nuvem seja transparente para os clientes, nos bastidores, distintas tecnologias trabalham em conjunto para oferecer suporte a funcionalidades importantes, como elasticidade e alta disponibilidade [Márquez et al 2018]. De uma perspectiva de infraestrutura, os processadores multi-core aprimoraram a capacidade de processamento e o ressurgimento da virtualizac ¸ão proporcionou maior flexibilidade de provisionamento para atender às demandas dos clientes.…”

Section: Computac ¸ãO De Alto Desempenho Na Nuvemunclassified

“…De uma perspectiva de infraestrutura, os processadores multi-core aprimoraram a capacidade de processamento e o ressurgimento da virtualizac ¸ão proporcionou maior flexibilidade de provisionamento para atender às demandas dos clientes. Do ponto de vista do software, arquiteturas distribuídas, como microsservic ¸os, permitiram um melhor uso dos recursos, dando origem a aplicac ¸ões projetadas para obter o melhor da nuvem [Márquez et al 2018].…”

Section: Computac ¸ãO De Alto Desempenho Na Nuvemunclassified

See 1 more Smart Citation

Otimizando a Execução de Aplicações Paralelas em Ambiente de Nuvem Heterogênea

Lima

Luizelli²,

Rossi³

et al. 2022

Anais Do XXIII Simpósio Em Sistemas Computacionais De Alto Desempenho (SSCAD 2022)

View full text Add to dashboard Cite

A computação na nuvem emerge como uma plataforma alternativa para a execução de aplicações de alto desempenho. Simultaneamente, a atualização de nodos computacionais nestes sistemas pode levar a uma heterogeneidade de recursos. Neste sentido, o desafio de executar aplicações paralelas na nuvem não está apenas relacionado a definição do melhor número de threads para a aplicação, mas também, a escolha ideal da arquitetura que irá executar tal aplicação. No entanto, as características de grau de paralelismo e capacidade computacional têm sido pouco exploradas para fazer a alocação de aplicações numa nuvem heterogênea. Portanto, neste artigo, mostramos que ao considerar o grau de paralelismo de uma aplicação e as características do nodo computacional, ganhos significativos de desempenho e consumo de energia podem ser obtidos quando comparado a maneira padrão com que aplicações são escalonadas num ambiente de nuvem heterogênea.

show abstract

Section: Computac ¸ãO De Alto Desempenho Na Nuvemunclassified

Otimizando a Execução de Aplicações Paralelas em Ambiente de Nuvem Heterogênea

Lima

Luizelli²,

Rossi³

et al. 2022

Anais Do XXIII Simpósio Em Sistemas Computacionais De Alto Desempenho (SSCAD 2022)

View full text Add to dashboard Cite

show abstract

“…In the microservices context, scalability is the service's ability to cope and perform under high demand. A scalable microservice adapts itself to the needs of its consumers [MVA18]. It is possible to scale those services by running multiple instances of them; each instance of the same service should be able to replace any other so that if one fails or already has high traffic, another working instance may be used in its place (see service E in Figure 5.5).…”

Section: Scalability and Service Discoverymentioning

confidence: 99%

Reducing Incidents in Microservices by Repaying Architectural Technical Debt

Toledo

Martini

Sjøberg

et al. 2021

2021 47th Euromicro Conference on Software Engineering and Advanced Applications (SEAA)

View full text Add to dashboard Cite

Background: Software systems must continuously evolve to meet new business requirements. A modular software architecture is key to facilitating the evolution of the system. Many software development organizations also require their software to be deployed on the cloud due to demands on scalability and availability. Microservices is an architectural style that allows the implementation of all these requirements. However, software architecture is prone to sub-optimal solutions, because of several factors such as time constraints, uncertainty, miscommunication, and the growing complexity of software systems. Such factors may lead to architectural technical debt (ATD). There are only a few studies about ATD in the context of microservices (MS-ATDs).Objective: This work aims to understand what MS-ATDs are, including their costs and solutions, and investigate methods to support their quantification, prioritization, and management.Method: The reported studies combined qualitative and quantitative research methods. We started with a multiple case study in seven large software development organizations to identify MS-ATDs, costs, and solutions. We then proceeded with an in-depth multiple case study in four large software development organizations on how a specific MS-ATD, the misuse of shared libraries, affects development agility. Next, we performed another multiple case study in three large software development organizations in the early stages of migration to microservices to understand how MS-ATDs occur during migration and how they can be prioritized. Finally, we conducted a quantitative case study in a large company before and after refactoring some MS-ATDs to understand how the refactoring affected the occurrence of incidents. We used incidents as a proxy of MS-ATD costs.Results: Our results include a catalog of MS-ATDs, their causes, their solutions, a quantification of the debts' interest based on the number of incidents resulting from the debts, and an approach to prioritize MS-ATDs. Examples of MS-ATDs are the lack of communication standards among microservices, the misuse of shared libraries, and an excessive number of small products. We report negative effects of misusing shared libraries on development agility. We also presented suggestions of how software development organizations could deal iii Abstract with this problem. Finally, we proposed a systematic prioritization approach for MS-ATDs based on factors such as the likelihood of their occurrence, the difficulty of their resolution, and their importance for the practitioners.Conclusion: Software development organizations are still learning how to use microservices and pay a high interest due to the lack of experience with this architectural style. Such organizations can use our catalog to identify 16 different MS-ATDs, their costs, and solutions. They can also integrate our lightweight MS-ATD prioritization approach into their agile development processes. Researchers can find our results valuable in understanding MS-ATDs and contributing to reducing the...

show abstract

“…According to Chris Richardson's Scale Cube, a threedimension scalability model [21], scaling in Microservice Architecture (MSA) corresponds to Yaxis scaling. It suggests the decomposition of a software application into multiple, distinct autonomous services.…”

Section: Introductionmentioning

confidence: 99%

A Comprehensive Microservice Extraction Approach Integrating Business Functions and Database Entities

Bajaj,

Goel,

Gupta

2024

IAJIT

View full text Add to dashboard Cite

Cloud application practitioners are building large-scale enterprise applications as microservices, to leverage scalability, performance, and availability. Microservices architecture allows a large monolithic application to be split into small, loosely coupled services. A service communicates with other services using lightweight protocols such as RESTful APIs. Extracting microservices from the monolith is a challenging task and is mostly performed manually by system architects based on their skills. This extraction involves both: 1) Partitioning of business logic, 2) Partitioning of database. For partitioning of business logic, the existing research studies focus on decomposition by considering the dependencies in the application at the class-level. However, with the passage of time, monolith application classes outgrow their size defying the Single Responsibility Principle (SRP). So, there is a need to consider the code within the classes when identifying microservices. Current studies also lack the partitioning of database and ignore the mapping of Database Entities (DE) to the microservices. In this paper, we present a Comprehensive Microservice Extraction Approach (CMEA) that considers: 1) Both classes and their methods to define and refine microservices, 2) Associate the DE to microservices using newly devised eight guiding rules handling ownership conflicts. This approach has been applied to three benchmark web applications implemented in Java and one in-house application implemented in both Java and Python. Our results demonstrate better or similar software quality attributes in comparison to the existing related studies. CMEA improves software quality attributes by 22%. System architects can easily identify microservices along with their DE using our approach. The CMEA is generic and language-independent so it can be used for any application

show abstract

A pattern language for scalable microservices-based systems

Cited by 12 publications

References 10 publications

Otimizando a Execução de Aplicações Paralelas em Ambiente de Nuvem Heterogênea

Otimizando a Execução de Aplicações Paralelas em Ambiente de Nuvem Heterogênea

Reducing Incidents in Microservices by Repaying Architectural Technical Debt

A Comprehensive Microservice Extraction Approach Integrating Business Functions and Database Entities

Contact Info

Product

Resources

About