A microservice‐based architecture for (customisable) analyses of Docker images

Brogi, Antonio; Neri, Davide; Soldani, Jacopo

doi:10.1002/spe.2583

Cited by 8 publications

(6 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For instance, we exploited Toskose to further validate the outcomes of our former research, that is, we exploited it to run TOSCA application specification automatically completed by TosKeriser 17 . The latter is a tool for completing TOSCA application specifications, which automatically discovers and includes the Docker containers offering all what needed to run the components of an application, based on the information automatically retrieved by DockerFinder 37 . Application specification generated by TosKeriser were translated to Docker Compose files, which were then effectively orchestrated on existing Docker‐based container orchestrators in a component‐aware manner.…”

Section: Discussionmentioning

confidence: 99%

Component‐aware orchestration of cloud‐based enterprise applications, from TOSCA to Docker and Kubernetes

et al. 2020

Self Cite

View full text Add to dashboard Cite

Enterprise IT is currently facing the challenge of coordinating the management of complex, multicomponent applications across heterogeneous cloud platforms. Containers and container orchestrators provide a valuable solution to deploy multicomponent applications over cloud platforms, by coupling the lifecycle of each application component to that of its hosting container. We hereby propose a solution for going beyond such a coupling, based on the OASIS standard TOSCA and on Docker. We indeed propose a novel approach for deploying multicomponent applications on top of existing container orchestrators, which enables managing each component independently from the container used to run it. We also present prototype tools that implement our approach, and we show how we effectively exploited them to carry out a concrete case study.

show abstract

Section: Discussionmentioning

confidence: 99%

Component‐aware orchestration of cloud‐based enterprise applications, from TOSCA to Docker and Kubernetes

et al. 2020

Self Cite

View full text Add to dashboard Cite

show abstract

“…With T os K er ISER, developers can only specify the software components forming an application, each together with the software distributions it needs to run. Obtained (incomplete) specifications can then be passed to T os K er ISER, which interacts with DOCKERANALYSER to search for Docker containers and which automatically completes them with Docker containers offering the software support needed by the application components. Completed specification can then be effectively orchestrated by T os K er .…”

Section: Discussionmentioning

confidence: 99%

TosKer: A synergy between TOSCA and Docker for orchestrating multicomponent applications

2018

Self Cite

View full text Add to dashboard Cite

Summary How to flexibly manage complex applications across heterogeneous cloud platforms is one of the main concerns in today's IT enterprise. The OASIS standard TOSCA (Topology and Orchestration Specification for Cloud Applications) and the Docker ecosystem are two emerging solutions trying to address this problem from different perspectives. In this paper, we propose a solution that tries to synergically combine the pros of both TOSCA and of Docker. More precisely, we propose a TOSCA‐based representation for specifying the software components and the Docker containers forming an application. We also present TosKer, an engine for orchestrating the management of multicomponent applications based on the proposed TOSCA representation and on Docker. Finally, we illustrate how TosKer was fruitfully exploited in a concrete case study based on a third‐party application.

show abstract

“…Then we can find the specific exception by extracting span information and comparing the exception table. The exception table can be established according to the experience of developers, which records the call parameters of standard exceptions [22].…”

Section: Exception Analysismentioning

confidence: 99%

Service Call Chain Analysis for Microservice Systems

Hao¹,

Hao²,

Zhang³

et al. 2022

Journal of Internet Technology

View full text Add to dashboard Cite

<p>Industrial practitioners widely adopt the microservice architecture to build applications. An application with microservice architecture can be composed of a set of individual services. Although microservice can improve the scalability of a system by isolating services, the complexity and difficulty of defect detection and analysis grow. High verification cost, a long feedback cycle, and high communication cost pose challenges to the maintenance of microservice systems. To address the problem, we propose a call chain tracing and analysis approach designed for the microservice architecture. To evaluate its effectiveness, we implement our approach as a plugin, namely Cam, to monitor and analyze exceptions by tracing call chains. Currently, Cam is packaged as a maven plugin for applications using Spring Cloud, which is an opensource microservice framework for Java programs. We experiment it with a microservice system to demonstrate its availability. The result shows that Cam can help software engineers understand the workflow of a service call and locate potential defects.</p> <p> </p>

show abstract

A microservice‐based architecture for (customisable) analyses of Docker images

Cited by 8 publications

References 10 publications

Component‐aware orchestration of cloud‐based enterprise applications, from TOSCA to Docker and Kubernetes

Component‐aware orchestration of cloud‐based enterprise applications, from TOSCA to Docker and Kubernetes

TosKer: A synergy between TOSCA and Docker for orchestrating multicomponent applications

Service Call Chain Analysis for Microservice Systems

Contact Info

Product

Resources

About