Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ Estudo Geralarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
Estudo Geral
Master thesis . 2018
Data sources: Estudo Geral
addClaim

Monitoria de Arquiteturas de Micro-serviços

Authors: Pina, Fábio Figueiredo;

Monitoria de Arquiteturas de Micro-serviços

Abstract

Uma das tendências mais recentes nos sistemas distribuídos é a de subdividir grandes componentes de software em pedaços mais pequenos. Este paradigma é conhecido por “micro-serviços” e, embora simplifique o desenvolvimento, instalação e gestão do software, torna o sistema mais complexo e bastante mais difícil de observar, dado o grande número de interações envolvidas. Por esta razão, num sistema de grandes dimensões, é particularmente difícil saber quais os componentes que mais contribuem para o tempo de espera medido pelos utilizadores. Por um lado, estes componentes não podem ser analisados separadamente; por outro, sem “instrumentar” extensivamente o código fonte é difícil relacioná-los para identificar a origem de estrangulamentos. Para mitigar este problema propomos uma abordagem bem mais simples: usando a gateway de acesso aos micro-serviços registamos todos as invocações que lhes são feitas, bem como todas as respostas, extraindo assim o relacionamento entre serviços e o respetivo desempenho. Para validar este método, simulamos a invocação de serviços concretos duma implementação real de uma aplicação. Os resultados mostram que é possível extrair a informação de desempenho mais relevante no sistema a um baixo custo. .

Breaking large software systems into smaller functionally interconnected components is a trend on the rise. This architectural style, known as “microservices”, simplifies development, deployment and management at the expense of complexity and observability. In fact, in large scale systems, it is particularly difficult to determine the set of microservices responsible for delaying a client’s request, when one module impacts several other microservices in a cascading effect. Components cannot be analyzed in isolation, and without instrumenting their source code extensively, it is difficult to find the bottlenecks and trace their root causes. To mitigate this problem, we propose a much simpler approach: log gateway activity, to register all calls to and between microservices, as well as their responses, thus enabling the extraction of topology and performance metrics, without changing source code. For validation, we implemented the proposed platform, with a microservices-based application that we observe under load. Our results show that we can extractrelevant performance information with a negligible effort. .

Dissertação de Mestrado em Engenharia Informática apresentada à Faculdade de Ciências e Tecnologia

Outro - Data Science para Não-Programadores PTDC/EEI-ESS/1189/2014

Country
Portugal
Related Organizations
Keywords

monitoria de caixa-preta, microservices, micro-serviços, API gateway, black-box monitoring

  • BIP!
    Impact byBIP!
    selected citations
    These citations are derived from selected sources.
    This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    0
    popularity
    This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
    Average
    influence
    This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    Average
    impulse
    This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
    Average
Powered by OpenAIRE graph
Found an issue? Give us feedback
selected citations
These citations are derived from selected sources.
This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Citations provided by BIP!
popularity
This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
BIP!Popularity provided by BIP!
influence
This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Influence provided by BIP!
impulse
This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
BIP!Impulse provided by BIP!
0
Average
Average
Average
Green