To see the other types of publications on this topic, follow the link: Docker.
Dissertations / Theses on the topic 'Docker'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'Docker.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
Littley, Michael Brian. "Towards a Scalable Docker Registry." Thesis, Virginia Tech, 2018. http://hdl.handle.net/10919/83814.
Full textAbstract:
Containers are an alternative to virtual machines rapidly increasing in popularity due to
their minimal overhead. To help facilitate their adoption, containers use management systems
with central registries to store and distribute container images. However, these registries
rely on other, preexisting services to provide load balancing and storage, which limits
their scalability. This thesis introduces a new registry design for Docker, the most prevalent
container management system. The new design coalesces all the services into a single,
highly scalable, registry. By increasing the scalability of the registry, the new design greatly
decreases the distribution time for container images. This work also describes a new Docker
registry benchmarking tool, the trace player, that uses real Docker registry workload traces
to test the performance of new registry designs and setups.Master of Science
2
Малець, Ігор Остапович, Олег Андрійович Андрушко, and Микола Анатолійович Панасюк. "Docker-технології в побудові мікросервісів." Thesis, Львівський державний університет безпеки життєдіяльності, 2017. http://hdl.handle.net/123456789/4286.
Full textAbstract:
Висвітлено складність командної роботи в процесі розробки програмних продуктів за умови віддаленого
доступу. Доповнено існуючий багаж знань про технології контейнеризації в світлі особливостей використання
Docker для побудови мікросервісів. Визначено особливості використання та основні переваги Docker-
технологій в процесі побудови мікросервісів.
3
Popolo, Ciro William Giovanni. "Docker: analisi sull'uso e sulla diffusione." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2018. http://amslaurea.unibo.it/15160/.
Full textAbstract:
Questa tesi descrive un'analisi sull'uso e sulla diffusione dei container software generati dalla piattaforma Docker. L'oggetto del lavoro della tesi consiste in un programma, personalizzabile, che analizza repository software della piattaforma github e ne stila delle statistiche. Tali statistiche saranno analizzate tramite l'uso di grafici. Inoltre ci sarà uno studio sull'uso che viene fatto di docker da parte degli utenti di github. Tale studio viene realizzato tramite l'analisi manuale di un campione di repository che soddisfano certi requisiti.
4
Henriksson, Oscar, and Michael Falk. "Static Vulnerability Analysis of Docker Images." Thesis, Blekinge Tekniska Högskola, Institutionen för datalogi och datorsystemteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-14794.
Full textAbstract:
Docker is a popular tool for virtualization that allows for fast and easy deployment of applications and has been growing increasingly popular among companies. Docker also include a large library of images from the repository Docker Hub which mainly is user created and uncontrolled. This leads to low frequency of updates which results in vulnerabilities in the images. In this thesis we are developing a tool for determining what vulnerabilities that exists inside Docker images with a Linux distribution. This is done by using our own tool for downloading and retrieving the necessary data from the images and then utilizing Outpost24's scanner for finding vulnerabilities in Linux packages. With the help of this tool we also publish statistics of vulnerabilities from the top downloaded images of Docker Hub. The result is a tool that can successfully scan a Docker image for vulnerabilities in certain Linux distributions. From a survey over the top 1000 Docker images it has also been shown that the amount of vulnerabilities have increased in comparison to earlier surveys of Docker images.
5
Wiens, Tobias. "Docker Orchestration for Scalable Tasks and Services." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-187015.
Full textAbstract:
Distributed services and tasks, i.e. large-scale data processing (Big Data), in the cloud became popular in recent years. With it came the possibility, to scale infrastructure according to the current demand, which promises to reduce costs. However, running and maintaining a company internal cloud, which is extended to one or more public clouds (hybrid cloud) is a complex challenge. In the recent years, Docker containers became very popular with the promise to solve compatibility issues in hybrid clouds. Packaging software with their dependencies inside Docker containers, promises less incompatibility issues. Combining hybrid clouds and Docker Containers, leads to a more cost effective, reliable and scalable data processing in the cloud. The problem solved in this thesis is: how to manage hybrid clouds, which run scalable distributed tasks or services. Fluctuating demand requires adding or removing computers from the current infrastructure, and changes dependencies, which are necessary to execute tasks or services. The challenge is, to provide all dependencies for a reliable execution of tasks or services. Furthermore, distributed tasks and services need to have the ability to communicate even on a hybrid infrastructure. The approach of this thesis is, to prototype three different Docker integrations for Activeeon’s ProActive, a hybrid cloud middleware. Further, each of the prototypes is evaluated, and one prototype is improved to an early stage product. The software-defined networks weave and flannel are benchmarked, in their impact on the network performance. How Docker containers affect the CPU, memory and disk performance is analyzed through literature review. Finally, the distributed large-scale data processing software Apache Flink is benchmarked inside containers, to measure the impact of containerizing a distributed large-scale data processing software. The results of this thesis show that Docker container orchestration is feasible with ProActive and software defined networks (weave and flannel). While both show impact on the pure network performance, the Apache Flink benchmark did not reveal any impact of using containers and software defined networks. Therefore, Docker containers together with orchestration through ProActive are able to form a large-scale data processing platform.Distributed Services eller Tasks, exempelvis storskalig data (Big data), i moln-lösningar har blivit populärt under de senaste åren. Med detta följer möjligheten att skala om infrastrukturen till den rådande efterfrågan, med syfte att minska kostnader. Men att köra och underhålla ett företags interna moln, som är kopplat till ett eller fler offentliga moln (Hybrid-moln) är en komplex utmaning. Under de senaste åren har Dockers blivit mycket populära, detta med syfte att lösa kompabilitets problem i hybrid-moln. Att paketera mjukvara med dess delar inuti en Docker medför färre kompabilitetsproblem. Att kombinera hybrid-moln och Dockers leder till en mer kostnadseffektiv, pålitlig och skalbar datahantering i molnet. Problemet som har lösts i denna uppsatts är: Hur kan man hantera hybrid-moln som kör Distributed Services och Tasks. Varierande efterfrågan kräver att man lägger till eller tar bort datorer från den nuvarande nätverk, samt att man ändrar beroendeförhållanden vilka är nödvändiga för att utföra uppgifter eller service. Utmaningen ligger i att tillhandahålla alla delar för ett säkert genomförande av uppgiften eller servicen. Vidare krävs även att Distributed Services och Tasks har möjlighet att kommunicera även om det är i en hybrid-molns lösning. Syftet med denna uppsats är att skapa tre olika prototyper av Docker-behållare för Activeeon´s ProActive, en hybrid-molns middleware. Vidare är varje prototyp utvärderad, en av prototyperna är även vidareutvecklad till ett tidigt produktstadie. Det mjukvarudefinerade nätverken weave och flannel är benchmarkade i deras påverkan på nätverket. Hur Dockers påverkar CPU:n, minnet och diskeffekten är analyserat i en litteraturstudie. Slutligen är mjukvaran Apache Flink Benchmarkad inuti Dockers-behållarna, detta för att kunna mäta effekten av en paketerad och distribuerad storskalig datahanterings mjukvara. Resultatet av denna studie visar att Dockers-behållarens samansättning är passande med ProActive och mjukvarunätverk (Weave och Flannel). Båda visar påverkan på den rena nätverkseffektiviteten men Apache Flink benchmarkingen visade inte någon påverkan av att använda behållare och mjukvarudefinerade nätverk. Därav ger samansättning av Dockers-behållare genom ProActive möjligheten att skapa en plattform att processa storskalig data.
6
Ginka, Anusha, and Venkata Satya Sameer Salapu. "Optimization of Packet Throughput in Docker Containers." Thesis, Blekinge Tekniska Högskola, Institutionen för datavetenskap, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-17787.
Full textAbstract:
Container technology has gained popularity in recent years, mainly because it enables a fast and easy way to package, distribute and deploy applications and services. Latency and throughput have a high impact on user satisfaction in many real-time, critical and large-scale online services. Although the use of microservices architecture in cloud-native applications has enabled advantages in terms of application resilience, scalability, fast software delivery and the use of minimal resources, the packet processing rates are not correspondingly higher. This is mainly due to the overhead imposed by the design and architecture of the network stack. Packet processing rates can be improved by making changes to the network stack and without necessarily adding more powerful hardware. In this research, a study of various high-speed packet processing frameworks is presented and a software high-speed packet I/O solution i.e., as hardware agnostic as possible to improve the packet throughput in container technology is identified. The proposed solution is identified based on if the solution involves making changes to the underlying hardware or not. The proposed solution is then evaluated in terms of packet throughput for different container networking modes. A comparison of the proposed solution with a simple UDP client-server application is also presented for different container networking modes. From the results obtained, it is concluded that packet mmap client-server application has higher performance when compared with simple UDP client-server application.
7
Camoli, Filippo <1996>. "Analysis of Cryptographic Vulnerabilities in Docker Images." Master's Degree Thesis, Università Ca' Foscari Venezia, 2022. http://hdl.handle.net/10579/21941.
Full textAbstract:
The thesis work consists in the research and analysis of the cryptographic non-conformities present in some docker images. We will illustrate the automation process for the collection of statistical samples aimed at determining the presence of vulnerabilities related to the mechanisms of cryptographic keys and certificates present in the aforementioned images and classifying them to understand whether the detected threats are actually real or instead attributable to cases deemed safe. Finally, we will discuss why such non-conformities exist and illustrate possible corrective solutions to eliminate these threats.
8
Alansari, Hayder. "Clustered Data Management in Virtual Docker Networks Spanning Geo-Redundant Data Centers : A Performance Evaluation Study of Docker Networking." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-141681.
Full textAbstract:
Software containers in general and Docker in particular is becoming more popular both in software development and deployment. Software containers are intended to be a lightweight virtualization that provides the isolation of virtual machines with a performance that is close to native. Docker does not only provide virtual isolation but also virtual networking to connect the isolated containers in the desired way. Many alternatives exist when it comes to the virtual networking provided by Docker such as Host, Macvlan, Bridge, and Overlay networks. Each of these networking solutions has its own advantages and disadvantages. One application that can be developed and deployed in software containers is data grid system. The purpose of this thesis is to measure the impact of various Docker networks on the performance of Oracle Coherence data grid system. Therefore, the performance metrics are measured and compared between native deployment and Docker built-in networking solutions. A scaled-down model of a data grid system is used along with benchmarking tools to measure the performance metrics. The obtained results show that changing the Docker networking has an impact on performance. In fact, some results suggested that some Docker networks can outperform native deployment. The conclusion of the thesis suggests that if performance is the only consideration, then Docker networks that showed high performance can be used. However, real applications require more aspects than performance such as security, availability, and simplicity. Therefore Docker network should be carefully selected based on the requirements of the application.
9
Savini, Gianni. "Virtualizzazione mediante software container: un approfondimento su Docker." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2019. http://amslaurea.unibo.it/18171/.
Full textAbstract:
La tesi tratta dei software container, una recente tecnologia di virtualizzazione facendo approfondimenti su Docker, in quanto soluzione maggiormente utilizzata e diffusa. In particolare si descrivono inizialmente che cosa siano, e cosa ha portato al loro sviluppo ed utilizzo, descrivendone l'evoluzione e le possibili soluzioni disponibili, ed esponendone i vantaggi che offrono. Nella parte centrale si usa Docker come soluzione di riferimento, spiegandone l'architettura e il funzionamento di base tramite alcuni esempi. Inoltre, si vedranno alcuni tool nativi per la gesione di sistemi più artilcolati. Infine si vedrà come questi si combinino bene con le architetture a microservizi e si vedrà come gestire questi microservizi.
10
Civolani, Lorenzo. "Fast Docker Container Deployment in Fog Computing infrastructures." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2019. http://amslaurea.unibo.it/17701/.
Full textAbstract:
I contenitori software, meglio noti come container, realizzano ambienti virtuali in cui molteplici applicazioni possono eseguire senza il rischio di interferire fra di loro.
L'efficienza e la semplicità dell'approccio hanno contribuito al forte incremento della popolarità dei contaier, e, tra le varie implementazioni disponibili, Docker è di gran lunga quella più diffusa.
Sfortunatamente, a causa delle loro grandi dimensioni, il processo di deployment di un container da un registro remoto verso una macchina in locale tende a richiedere tempi lunghi.
La lentezza di questa operazione è particolarmente svantaggiosa in un'architettura Fog computing, dove i servizi devono muoversi da un nodo all'altro in risposta alla mobilità degli utenti.
Tra l'altro, l'impiego di server a basse prestazioni tipico di tale paradigma rischia di aggravare ulteriormente i ritardi.
Questa tesi presenta FogDocker, un sistema che propone un approccio originale all'operazione di download delle immagini Docker con l'obiettivo di ridurre il tempo necessario per avviare un container.
L'idea centrale del lavoro è di scaricare soltanto il contenuto essenziale per l'esecuzione del container e procedere immediatamente con l'avvio; poi, in un secondo momento, mentre l'applicazione è già al lavoro, il sistema può proseguire col recupero della restante parte dell'immagine.
I risultati sperimentali confermano come FogDocker sia in grado di raggiungere una riduzione notevole del tempo necessario per avviare un container.
Tale ottimizzazione si rivela essere particolarmente marcata quando applicata in un contesto a risorse computazionali limitate.
I risultati ottenuti dal nostro sistema promettono di agevolare l'adozione dei software container nelle architetture di Fog computing, dove la rapidità di deployment è un fattore di vitale importanza.
11
Erlandsson, Rickard, and Eric Hedrén. "Improving Software Development Environment : Docker vs Virtual Machines." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-210667.
Full textAbstract:
The choice of development environment can be crucial when it comes to developing a software. Few researches exist on comparing development environments. Docker is a relatively new software for handling and setting up container-environments. In this research, the possibility of using Docker as a software development environment is being investigated and compared against virtual machines as a development environment. The purpose of this research is to examine how the choice of development environment affect the development process. The work was qualitative, with an inductive and a deductive approach. It included a case study with two phases. One in which virtual machines and one in which Docker were used to implement a development environment. Observations were made after each implementation. The data from each implementation were then compared and evaluated against each other. The results from the comparisons and the evaluation clearly shows that the choice of development environment can influence the process of developing software. Different development environments affect the development process differently, both good and bad. With Docker, it’s possible to run more environments at once than when using virtual machines. Also, Docker stores the environments in a clever way that results in the environments taking up less space on the secondary storage compared to virtual machine environments. This is due to that Docker uses a layer system when it comes to containers and their components. When using Docker, no Graphical User Interface (GUI) to install and manage applications inside a container is provided, this can be a drawback since some developers may need a GUI to work. The lack of a GUI makes it harder to get an Integrated Development Environment (IDE) to work properly with a container to for example debug code.Valet av utvecklingsmiljö kan vara avgörande vid utveckling av mjukvara. Få undersökningar finns idag angående jämförelser mellan utvecklingsmiljöer. Docker är en relativt ny mjukvara för att sätta upp samt hantera container- miljöer. I denna undersökning, kommer möjligheten att använda Docker som utvecklingsmiljö att undersökas och jämföras mot virtuella maskiner som utvecklingsmiljö. Syftet med undersökningen är att se hur valet av utvecklingsmiljö påverkar utvecklingsprocessen av en mjukvara. Arbetet bedrevs på ett kvalitativt sätt, med både ett induktivt samt ett deduktivt tillvägagångssätt. Det inkluderade även en fältstudie med två faser. En där virtuella maskiner och en där Docker användes till att implementera en utvecklingsmiljö. Observationer utfördes efter varje implementation. Data från varje implementation jämfördes och evaluerades mot varandra. Resultaten från jämförelserna och evalueringen visar att valet av utvecklingsmiljö har inflytande på processen av utveckling av mjukvara. Olika utvecklingsmiljöer påverkar utvecklingsprocessen olika, både på bra och dåliga sätt. Med Docker är det möjligt att köra fler miljöer samtidigt än vad som är möjligt vid användande av virtuella maskiner. Docker lagrar även miljöerna på ett smart sätt, som gör att de tar upp mindre plats på den sekundära lagringen jämfört med virtuella maskiner. Detta är på grund av att Docker använder sig av ett lager-system när det gäller containrar och deras komponenter. När Docker används, tillhandhålls inget Graphical User Interface (GUI) för att installera eller hanterar applikationer inuti en container, detta kan vara en nackdel då vissa utvecklare kan behöva ett GUI för att arbeta. Avsaknaden av ett GUI gör det svårare att få en Integrated Development Environment (IDE) att fungera ordentligt med en container för att till exempel avlusa kod.
12
Adolfsson, Henrik. "Comparison of Auto-Scaling Policies Using Docker Swarm." Thesis, Linköpings universitet, Databas och informationsteknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-154160.
Full textAbstract:
When deploying software engineering applications in the cloud there are two similar software components used. These are Virtual Machines and Containers. In recent years containers have seen an increase in popularity and usage, in part because of tools such as Docker and Kubernetes. Virtual Machines (VM) have also seen an increase in usage as more companies move to solutions in the cloud with services like Amazon Web Services, Google Compute Engine, Microsoft Azure and DigitalOcean. There are also some solutions using auto-scaling, a technique where VMs are commisioned and deployed to as load increases in order to increase application performace. As the application load decreases VMs are decommisioned to reduce costs. In this thesis we implement and evaluate auto-scaling policies that use both Virtual Machines and Containers. We compare four different policies, including two baseline policies. For the non-baseline policies we define a policy where we use a single Container for every Virtual Machine and a policy where we use several Containers per Virtual Machine. To compare the policies we deploy an image serving application and run workloads to test them. We find that the choice of deployment strategy and policy matters for response time and error rate. We also find that deploying applications as described in the methodis estimated to take roughly 2 to 3 minutes.
13
Davidsson, Pontus, and Niklas Englund. "Docker forensics: Investigation and data recovery on containers." Thesis, Högskolan i Halmstad, Akademin för informationsteknologi, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-42498.
Full textAbstract:
Container technology continuously grows in popularity, and the forensic area is less explored than other areas of research concerning containers. The aim of this thesis is, therefore, to explore Docker containers in a forensic investigation to test whether data can be recovered from deleted containers and how malicious processes can be detected in active containers. The results of the experiments show that, depending on which container is used, and how it is configured, data sometimes persists after the container is removed. Furthermore, file carving is tested and evaluated as a useful method of recovering lost files from deleted containers, should data not persist. Lastly, tests reveal that malicious processes running inside an active container can be detected by inspection from the host machine.
14
Wong, Sai Man. "An Evaluation of Software-Based Traffic Generators using Docker." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-224206.
Full textAbstract:
The Information and Communication Technology (ICT) industry and network researchers use traffic generator tools to a large extent to test their systems. The industry uses reliable and rigid hardware-based platform tools for high-performance network testing. The research community commonly uses software-based tools in, for example, experiments because of economic and flexibility aspects. As a result, it is possible to run these tools on different systems and hardware. In this thesis, we examine the software traffic generators Iperf, Mausezahn, Ostinato in a closed loop physical and virtual environment to evaluate the applicability of the tools and find sources of inaccuracy for a given traffic profile. For each network tool, we measure the throughput from 64- to 4096-byte in packet sizes. Also, we encapsulate each tool with container technology using Docker to reach a more reproducible and portable research. Our results show that the CPU primarily limits the throughput for small packet sizes, and saturates the 1000 Mbps link for larger packet sizes. Finally, we suggest using these tools for simpler and automated network tests.IT-branschen och nätverksforskare använder sig av trafikgeneratorer till stor del för att testa sina system. Industrin använder sig av stabila och pålitliga hårdvaruplattformar för högpresterande nätverkstester. Forskare brukar använda mjukvarubaserade verktyg i till exempel experiment på grund av ekonomiska och flexibilitet skäl. Det är därför möjligt att använda dessa verktyg på olika system och hårdvaror. I denna avhandling undersöker vi mjukvarutrafikgeneratorerna Iperf, Mausezahn, Ostinato i en isolerad fysisk och virtuell miljö, det vill säga för att utvärdera användbarheten av verktygen och hitta felkällor för en given trafikprofil. För varje nätverksverktyg mäter vi genomströmningen från 64 till 4096 byte i paketstorlekar. Dessutom paketerar vi varje verktyg med molnteknologin Docker för att nå ett mer reproducerbart och portabelt arbete. Våra resultat visar att processorn begränsar genomströmningen för små paketstorlekar och saturerar 1000 Mbps-länken för större paketstorlekar. Slutligen föreslår vi att man kan använda dessa verktyg för enklare och automatiserade nätverkstester.
15
Berg, Gustaf, and Magnus Brattlöf. "Distributed Checkpointing with Docker Containers in High Performance Computing." Thesis, Högskolan Väst, Avdelningen för data-, elektro- och lantmäteriteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:hv:diva-11645.
Full textAbstract:
Container-virtualisering har blivit mer och mer använt efter att uppdateringar till cgroups och namespace-funktionerna släpptes i Linuxkärnan. Samtidigt så lider industrins högpresterande beräkningskluster av dyra licenskostnader som skulle kunna hanteras av virtualisering. I den här uppsatsen utformades experiment för att ta reda på om Dockers funktion checkpoint, som fortfarande är under utveckling, skulle kunna utnyttjas i industrins beräkningskluster. Genom att demonstrera detta koncept och dess möjligheter att pausa distribuerade containrar, som kör parallella processer inuti, användes den välkända NAS Parallel Benchmarken (NPB) fördelad över två test-maskiner. Sedan så pausades containrar i olika ordningar och Docker lyckas återuppta benchmarken utan problem både lokalt och distribuerat. Om man försiktigt överväger ordningen som man skriver ner containers till disk (checkpoint) så går det utan problem att återuppta benchmarken lokalt på samma maskin. Slutligen så visar vi även att distribuerade containrar kan återupptas på en annan maskin än där den startade med hög framgång. Dockers prestanda, möjligheter och flexibilitet lämpar sig i framtidens industriella högpresterande kluster där man mycket väl kan köra sina applikationer i containrar istället för att köra dom på det traditionella sättet, direkt på hårdvaran. Genom användning av Docker-containers kan man hantera problemet med dyra licenskostnader och prioriteringar.Lightweight container virtualization has gained widespread adoption in recent years after updates to namespace and cgroups features in the Linux kernel. At the same time the Industrial High Performance community suffers from expensive licensing costs that could be managed with virtualization. To demonstrate that Docker could be used for suspending distributed containers with parallel processes, experiments were designed to find out if the experimental checkpoint feature is ready for this community. We run the well-known NAS Parallel Benchmark (NPB) inside containers spread over two systems under test to prove this concept. Then, pausing containers and unpausing them in different sequence orders we were able resume the benchmark. After that, we further demonstrate that if you carefully consider the order in which you Checkpoint/Restore containers, then the checkpoint feature is also able to resume the benchmark successfully. Finally, the concept of restoring distributed containers, running the benchmark, on a different system from where it started was proven to be working with a high success rate. Our tests demonstrate the performance, possibilities and flexibilities of Dockers future in the industrial HPC community. This might very well tip the community over to running their simulations and virtual engineering-applications inside containers instead of running them on native hardware.
16
Emilsson, Rasmus. "Container performance benchmark between Docker, LXD, Podman & Buildah." Thesis, Högskolan i Skövde, Institutionen för informationsteknologi, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:his:diva-18748.
Full textAbstract:
Virtualization is a much-used technology by small and big companies alike as running several applications on the same server is a flexible and resource-saving measure. Containers which is another way of virtualizing has become a popular choice for companies in the past years seeing even more flexibility and use cases in continuous integration and continuous development.This study aims to explore how the different leading container solutions perform in relation to one another in a test scenario that replicates a continuous integration use case which is compiling a big project from source, in this case, Firefox.The tested containers are Docker, LXD, Podman, and Buildah which will have their CPU and RAM usage tested while also looking at the time to complete the compilation. The containers perform almost on par with bare-metal except Podman/Buildah that perform worse during compilation, falling a few minutes behind.
17
Kjellstedt, Mattias. "PERFORMANCE EVALUATION OF DEPLOYING MICROSERVICE SUSING DOCKER AND PODMAN." Thesis, Umeå universitet, Institutionen för datavetenskap, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-175891.
Full textAbstract:
Containers are the latest generation of virtualization solutions. The most popular container solution has been Docker, but it struggles with security issues. A newer alternative is Podman, which solves the security issues while offering similar functionality. In this study I answer the question ”how does the overhead of Docker and Podman impact performance compared to native performance?”. The amount of overhead these two containers introduces are compared, along with native system performance by benchmarking CPU- memory- and disk performances.These benchmarks implies that the two containers have very similar and near-native performance and the choice of container solution is not a question of performance, but rather of user preferences: Do you want the added security? Podman. Do you already have your whole environment build around Docker and the security is not a problem? Stick with Docker.
18
Khan, Kafeel Ahmed. "Web-based Management of Fog Computing Services implemented in Docker." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2019. http://amslaurea.unibo.it/18934/.
Full textAbstract:
The aim and motivation of this thesis project is to introduce the implementation of the Fog computing scenario. For possible demonstration, we use the feasible or concur solution already deployed in the cloud computing paradigm. An emerging trend of IoT in the current era required more development in cloud computing due to the centralized control of resources that is no-more beneficial in the IoT base scenario. A distributed base approach called Fog computing is introduced that manages the services without being the use of a centralized pool of cloud. Although, Fog cannot fully function without being centralized control. But in order to implement the Fog node, I used a hypervisor supported device to configure virtual machines on the server and considered it as edge or fog node and make it capable to hold Fog services. Further, I used the docker container orchestration tool configure along with the Apache server that can host webpages to interact with the Docker API support and last a local machine that is used to access the fog node by a browser. Further, I analyze the response time of on-demand service with respect to the number of containers and conclude that using Fog as an intermittent node reduces the overall container formation time as compared to those users that directly connect with the cloud server this approach can fulfill some level of latency requirement by IoT devices.
19
Lubin, Eric M. Eng Massachusetts Institute of Technology. "VM2Docker : automating the conversion from virtual machine to docker container." Thesis, Massachusetts Institute of Technology, 2015. http://hdl.handle.net/1721.1/100683.
Full textAbstract:
Thesis: M. Eng., Massachusetts Institute of Technology, Department of Electrical Engineering and Computer Science, 2015.Cataloged from PDF version of thesis.
Includes bibliographical references (pages 66-68).
Container technology represents a flourishing field in cloud computing. For many types of computing, containers are a viable alternative to virtual machines because many applications do not require isolated kernels. Containers share the kernel with the host, as opposed to virtual machines which have a completely isolated kernel. Because of this distinction, containers are more lightweight and higher performing, but also have less isolation and therefore increased security concerns. The Docker framework, among other alternatives, has gotten the most attention and popularity over the past year and provides a powerful layered filesystem to improve deployability and provide space savings for those containers that share many layers in common. As of this writing, there is no system for automatically converting VMs to containers, as all configuration must be done manually. This is potentially unwieldy for system administrators looking to convert five to ten, or even hundreds, of virtual machines at once. This thesis presents a system we call VM2Docker that attempts to automate this conversion. VM2Docker specifically focuses on automatically generating layers for Docker to take advantage of the filesystem similarities across VMs of the same operating system. VM2Docker has been tested on various releases of Ubuntu, CentOS, and Mageia with a large degree of success and is able to provide filesystem space savings and deployment speed improvements with as few as 2 instances of a VM of a given operating system and release.
by Eric Lubin.
M. Eng.
20
Harshini, Nekkanti. "Measuring And Modeling Of Open vSwitch Performance : Implementation in Docker." Thesis, Blekinge Tekniska Högskola, Institutionen för kommunikationssystem, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13479.
Full textAbstract:
Network virtualization has become an important aspect of the Telecom industry. The need forefficient, scalable and reliable virtualized network functions is paramount to modern networking.Open vSwitch is such virtual switch that attempts to extend the usage of virtual switches to industrygrade performance levels on heterogeneous platforms.The aim of the thesis is to give an insight into the working of Open vSwitch. To evaluate theperformance of Open vSwitch in various virtualization scenarios such as KVM (second companionthesis)[1] and Docker. To investigate different scheduling techniques offered by the Open vSwitchsoftware and supported by the Linux kernel such as FIFO, SFQ, CODEL, FQCODEL, HTB andHFSC. To differentiate the performance of Open vSwitch in these scenarios and scheduling capacitiesand determine the best scenario for optimum performance.The methodology of the thesis involved a physical model of the system used for real-timeexperimentation as well as quantitative analysis. Quantitative analysis of obtained results paved theway for unbiased conclusions. Experimental analysis was required to measure metrics such asthroughput, latency and jitter in order to grade the performance of Open vSwitch in the particularvirtualization scenario.The results of the thesis must be considered in context with a second companion thesis[1]. Both thethesis aim at measuring the performance of Open v-Switch but the virtualization scenarios (Dockerand KVM) which are chosen are different, However, this thesis outline the performance of Open vSwitch and linux bridge in docker scenario. Various scheduling techniques were measured fornetwork performance metrics across both Docker and KVM (second companion thesis) and it wasobserved that Docker performed better in terms of throughput, latency and jitter. In Docker scenarioamongst the scheduling algorithms measured, it has almost same throughput in all schedulingalgorithms and latency shows slight variation and FIFO has least latency, as it is a simplest algorithmand consists of default qdisk. Finally jitter also shows variation on all scheduling algorithms.The conclusion of the thesis is that the virtualization layer on which Open vSwitch operates is one ofthe main factors in determining the switching performance. The KVM scenario and Docker scenarioeach have different virtualization techniques that incur different overheads that in turn lead to differentmeasurements. This difference occurs in different packet scheduling techniques. Docker performsbetter than KVM for both bridges. In the Docker scenario Linux bridge performs better than that ofOpen vSwitch, throughput is almost constant and FIFO has a least latency amongst all schedulingalgorithms and jitter shows more variation in all scheduling algorithms.
21
Сослуєв, О. В. "Система автоматизованого балансування навантаження для мікросервісної архітектурі на базі Docker." Thesis, Чернігів, 2020. http://ir.stu.cn.ua/123456789/23531.
Full textAbstract:
Сослуєв, О. В. Система автоматизованого балансування навантаження для мікросервісної архітектурі на базі Docker : випускна кваліфікаційна робота : 123 "Комп’ютерна інженерія" / О. В. Сослуєв ; керівник роботи Є. В. Риндич ; НУ "Чернігівська політехніка", кафедра інформаційних та комп’ютерних систем. – Чернігів, 2020. – 106 с.Дипломна робота має полягає в написанні конфігурації для веб-сайту. Конфігурація повинна працювати на всіх платформах як Linux, Windows, Mac OS. Docker - це дуже зручний інструмент для управління ізольованими Linux-контейнерами. За допомогою цього інструменту можна операційній системи запускати процеси в ізольованому оточенні на базі спеціально створених образів. Метою роботи є : -Проектування системи з використанням системи віртуалізації за допомогою інструменту Docker, що включає розробку и налаштування конфігурації. -Розробка конфігурації для автоматизованого балансування навантаження. -Можливість налаштування проценту переходу користувачів на сайт. Наприклад в системі банкінгу, є дві версії, одна з яких бета-версія сайту, друга це стара стабільна версія. Це необхідно для того щоб тестувальники на великих проєктах, витрачали менше ресурсів та часу на виконання тестів. Середній час відвідування сайту банку займає близько 30 хвилин. За останні роки розробники додатків та сайтів, хотіли щоб їх продукт стабільно працював на декількох платформах. Швидко запускався та розгортався за короткий час. Один раз витрачавши час на конфігурацію, а потім її використовуєш в декількох проектах де вона необхідна, значно спрощує розробку.
The subject of the thesis is to write the configuration for the website. The configuration must work on all platforms like Linux, Windows, Mac OS. Docker is a very handy tool for managing isolated Linux containers. With this tool, you can run the operating system processes in an isolated environment based on specially created images. The purpose of the work is: -Design the system using a virtualization system using the Docker tool, which includes the development and configuration of the configuration. -Configuration development for automated load balancing. -Ability to adjust the percentage of users coming to the site. For example, in the banking system, there are two versions, one of which is a beta version of the site, the other is an old stable version. This is necessary so that testers on large projects spend less resources and time on tests. The average time to visit the bank's website is about 30 minutes. In recent years, application and website developers have wanted their product to run stably on multiple platforms. It started up and deployed quickly in a short time. Once you spend time on the configuration, and then use it in several projects where it is needed, greatly simplifies development.
22
Ryding, Christian, and Rickard Johansson. "Jails vs Docker : A performance comparison of different container technologies." Thesis, Mittuniversitetet, Institutionen för data- och systemvetenskap, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:miun:diva-39517.
Full textAbstract:
Virtualization is used extensively by Enterprise IT architecture and cloud computing, it is used to provide customers a part of their hardware resources as a service. Container technology is the new generation of virtualization and provides performance benefits due to less overhead. Earlier research has compared different container technologies regarding their performance, including Docker which is the most popular container technology. Most of this research has been focusing on Linux based container technologies. Even though there is interest in knowing how other container technologies under different operating systems perform. In this study we explore the performance of Docker in contrast to the performance of a contending container technology named Jails. We present how well each container technology performs running one or multiple containers, in the areas of CPU, memory, read from disk, write to disk, network and startup time efficiency. The comparison was done using collected statistics from different benchmarking tools. Results from this study have shown that Docker is utilizing shared resources and has better stability compared to Jails. We also discuss what unexplored benefits Docker and Jails can have by implementing each other’s unique features. Future work could consist of writing to disk or reading from disk performance tests under one common filesystem, e.g., ZFS file system.Virtualisering används i stor utsträckning av Enterprise IT-arkitektur och molntjänster, den används för att kunna erbjuda sina kunder en del av sina hårdvaruresurser som en tjänst. Containerteknologi är den nya generationen virtualisering och ger prestandafördelar på grund av mindre omkostnader. Tidigare forskning har jämfört olika containerteknologier angående deras prestanda, inklusive Docker, som är den mest populära containertekniken. Merparten av tidigare forskning har fokuserat på Linuxbaserade containerteknologier, även om det finns intresse för att veta hur andra containerteknologier under olika operativsystem fungerar. I denna studie undersöker vi Dockers prestanda jämfört med prestandan till containerteknologin med namnet Jails. Vi presenterar hur bra varje containerteknologi fungerar med att köra en eller flera containrar inom områdena CPU, minne, läsa från disk, skriva till disk, nätverkshastighet och starttid. Jämförelsen gjordes med insamlad statistik från olika referensverktyg. Resultat från denna studie har visat att Docker använder delade resurser på ett effektivare sätt och har bättre stabilitet jämfört med Jails. Vi diskuterar också vilka outforskade fördelar Docker och Jails kan ha genom att implementera varandras unika funktioner. Framtida arbete kan bestå av att skriva till disk eller läsa från diskprestanda under ett gemensamt filsystem, t.ex. ZFS-filsystem.
23
Issa, Mubdir. "Performance Impact of Migrating a Mining Traffic Management System To Docker." Thesis, Karlstads universitet, Institutionen för matematik och datavetenskap (from 2013), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kau:diva-86037.
Full textAbstract:
Software deployment is all of the activities that make a software system available for use. An examaple of such activites can be installations, updating and removing of software. Each deployment platform can differ in quality attributes such as performance, maintainability, etc. Docker, a deployment platform using container technology offering a more modular way of deployment has become increasingly popular over the past few years. The aim of the project is to find out how a deployment with Docker would affect the performance of a clientserver application from the mining industry. Three scenarios were performed in a simulated environment for the existing as well as the potential deployment platform. Measures of roundtrip time were made for both sets of the scenarios. Results show a general decrease in performance when running the application on Docker. This is especially seen in early stages of each scenario, where Docker in average has 15 times higher roundtrip times than the existing platform. However, results gathered from each scenario suggests that while Docker does start much slower than the existing platform, in later stages of each scenarios, Docker manages to narrow the gap and be at most 1.14 times higher than the existing platform. In conclusion, while the deployment in which the existing platform is deployed on does out perform Docker, it still shows some promise and could potentially be a worthy option to look at for further work.
24
Andras, Balla. "A comparison between serverless and Docker container deployments : In the cloud." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-75163.
Full textAbstract:
Designing an application from top to bottom is a challenge for any software architect. Designing an application to be deployed in the cloud adds extra complexity and a variety of questions to the task. One of these questions is how to deploy an application? The most popular choices at this time are either Docker containers or serverless functions. This report presents a comparison between the two deployment methods based on cost and performance. The comparison did not yield a conclusive winner but it did offer some key pointers to help with the decision. Docker containers offer a standardized deployment method for a low price and with good performance. Before choosing Docker the intended market needs to be evaluated given that for each region Docker needs to serve, the price also increases. Serverless functions offer auto-scaling and easy global deployments but suffer from high complexity, slower performance, and an uncertain monthly price tag.
25
Johnson, Tobias, and Carl Lindell. "Docker Image Selenium Test : A proof of concept for automating testing." Thesis, Högskolan i Halmstad, Akademin för informationsteknologi, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-43032.
Full textAbstract:
The elderly social care IT company Phoniro is developing solutions for deploying software using docker technologies. To secure quality in their deploy pipelines Phoniro would like to do automatic selenium testing within Docker containers. The project should set the framework and required technical solution to enable this and also run some basic test including suitable reporting on test success. This is a concept that is new to Phoniro that would allow them, if proven, to automate testing in a safe environment, and pushing their web applications to deployment faster. The purpose is to prove this concept by creating a framework that will easily let the user run web applications inside a Docker container. Then run this framework inside of a pipeline to see the testing capabilities. The user is supposed to be able to do this without any previous knowledge of how docker works. We have developed a framework in Python that enables the user to build and run their web application inside a docker container. We built a pipeline and connected it to the repository with the source code for the web application. The framework is run inside the pipeline to start the container, followed by simple selenium tests that we created to test the concept. We have proven the concept to run and test web applications in docker containers inside of pipelines to work. It is possible connect a web application in development to a repository, connect it to a pipeline and have it automatically test the application every time a change is made to the source code. By designing proper selenium tests the pipeline can save a lot of time and effort that is otherwise spent on manual testing
26
Семенова, А. В. "Інформаційна система каталогізації бібліографічних описів з інтегрованим репозиторієм." Master's thesis, Сумський державний університет, 2020. https://essuir.sumdu.edu.ua/handle/123456789/82228.
Full text
27
Rappini, Alessandro. "Studio ed Analisi di tecniche di container migration con supporto alla persistenza in scenari di Edge Computing." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2020. http://amslaurea.unibo.it/21571/.
Full textAbstract:
Il numero di dispositivi IoT connessi alla rete è in costante aumento e con loro i dati da essi prodotti. Le tradizionali soluzioni di elaborazione e archiviazione dati non saranno più sufficientemente performanti in quanto la mole di dati crescerà in maniera esponenziale nei prossimi anni. Nuovi approcci spingono all'introduzione di uno strato intermedio tra il creatore del dato e il luogo dove deve essere depositato, uno di questi approcci è l'Edge computing; ma la gestione dei servizi in esecuzione al suo interno rappresenta una nuova sfida. Nella distribuzione di servizi si stanno evolvendo i container, i quali offrono il vantaggio di essere migrati tra calcolatori con una facilità maggiore rispetto a un'applicazione. In questo lavoro di tesi è stato creato un servizio che possa gestire e spostare container Docker, con annesso il proprio stato di esecuzione, in un cluster di nodi Edge. Lo sviluppo è stato impostato in un'ottica che prevede che vari nodi Edge connessi in rete possano creare in autonomia un cluster dove al suo interno sia presente un nodo Leader e diversi nodi Follower. L'elezione del Leader avviene tra i nodi scambiandosi un valore di fitness, che è compreso tra 0 e 1 ed indica quanto il nodo è performante. Il design dell'architettura è stato studiato per essere fault tolerance nei confronti del Leader e dei nodi Follower. Il Leader ha il compito principale di raccogliere i valori di fitness dai nodi Follower del cluster e indire la migrazione di container Docker sulla base di policy studiate ad hoc, le quali tengono conto anche dei valori fitness specifici su ogni singolo container. Il motivo che ha spinto la creazione dell'applicazione è quello di creare un servizio che effettui varie migrazioni al fine di uniformare i valori di fitness dei vari nodi del cluster.
28
Zhao, Nannan. "Towards a Flexible High-efficiency Storage System for Containerized Applications." Diss., Virginia Tech, 2020. http://hdl.handle.net/10919/100315.
Full textAbstract:
Due to their tight isolation, low overhead, and efficient packaging of the execution environment,
Docker containers have become a prominent solution for deploying modern applications.
Consequently, a large amount of Docker images are created and this massive image
dataset presents challenges to the registry and container storage infrastructure and so far
has remained a largely unexplored area. Hence, there is a need of docker image characterization that can help optimize and improve the storage systems for containerized applications. Moreover, existing deduplication techniques significantly degrade the performance of registries, which will slow down the container startup time. Therefore, there is growing demand for high storage efficiency and high-performance registry storage systems. Last but not
least, different storage systems can be integrated with containers as backend storage systems
and provide persistent storage for containerized applications. So, it is important to analyze
the performance of different backend storage systems and storage drivers and draw out the
implications for container storage system design. These above observations and challenges
motivate my dissertation.
In this dissertation, we aim to improve the flexibility, performance, and efficiency of the
storage systems for containerized applications. To this end, we focus on the following three
important aspects: Docker images, Docker registry storage system, and Docker container
storage drivers with their backend storage systems. Specifically, this dissertation adopts
three steps: (1) analyzing the Docker image dataset; (2) deriving the design implications;
(3) designing a new storage framework for Docker registries and propose different optimizations
for container storage systems.
In the first part of this dissertation (Chapter 3), we analyze over 167TB of uncompressed
Docker Hub images, characterize them using multiple metrics and evaluate the potential of
le level deduplication in Docker Hub. In the second part of this dissertation (Chapter 4),
we conduct a comprehensive performance analysis of container storage systems based on the
key insights from our image characterizations, and derive several design implications. In the
third part of this dissertation (Chapter 5), we propose DupHunter, a new Docker registry
architecture, which not only natively deduplicates layers for space savings but also reduces
layer restore overhead. DupHunter supports several configurable deduplication modes, which
provide different levels of storage efficiency, durability, and performance, to support a range
of uses. In the fourth part of this dissertation (Chapter 6), we explore an innovative holistic
approach, Chameleon, that employs data redundancy techniques such as replication and
erasure-coding, coupled with endurance-aware write offloading, to mitigate wear level imbalance in distributed SSD-based storage systems. This high-performance fash cluster can be used for registries to speedup performance.Doctor of Philosophy
The amount of Docker images stored in Docker registries is increasing rapidly and present challenges for the underlying storage infrastructures. Before we do any optimizations for the storage system, we should first analyze this big Docker image dataset. To this end, in this dissertation we perform the first large-scale characterization and redundancy analysis of the images and layers stored in the Docker Hub registry. Based on the findings, this dissertation presents a series of practical and efficient techniques, algorithms, optimizations to achieve high performance and flexibility, and space-efficient storage system for containerized applications. The experimental evaluation demonstrates the effectiveness of our optimizations and techniques to make storage systems flexible and space-efficacy.
29
Чорноног, О. А. "Розробка архітектури WEB-додатку PhotoBoom-у з використанням програмного забезпечення на Docker." Thesis, Чернігів, 2021. http://ir.stu.cn.ua/123456789/24975.
Full textAbstract:
Чорноног, О. А. Розробка архітектури WEB-додатку PhotoBoom-у з використанням програмного забезпечення на Docker / : випускна кваліфікаційна робота : 123 "Комп’ютерна інженерія" / О. А. Чорноног ; керівник роботи В. М. Базилевич ; НУ "Чернігівська політехніка", кафедра інформаційних і комп’ютерних систем. – Чернігів, 2021. – 79 с.Метою цієї роботи є написання WEB-додатку, що буде зберігати найважливіші моменти життя людини(фотографії). У проекті описано процес і результати розробки SPA- додатку, із розробкою Front-endу – максимально зручним дизайном для покращення взаємодії користувача з веб-додатком, Back-end – серверна частина проекту, продумування і написання програмної логіки, робота з базою даних. Цей WEB-додаток здійснює передачу інформації по протоколу HTTP. Робота веб-додатку можлива в будь-якому браузері. Для створення серверної частини було використано середовище виконання Node.js та мова програмування JavaScript. Для створення клієнтської частини було використано фреймворк Angular та мова програмування TypeScript, а також HTML та CSS. Для написання бази даних було використано MySQL. Подальший розвиток роботи можливий у сторону покращення інтерфейсу для створення зручнішої взаємодії користувача з веб-додатком, покращення роботи сервера і додавання функцій, які зможе виконувати сервер.
The purpose of this work is to write a WEB-application that will save the most important moments of human life (photos). The project describes the process and results of SPA application development, with Front-end development - the most convenient design to improve user interaction with the web application, Back-end - server part of the project, thinking and writing software logic, working with the database. This WEB-application transmits information via HTTP. The web application can work in any browser. Node.js runtime and JavaScript programming language were used to create the server part. The Angular framework and the TypeScript programming language, as well as HTML and CSS, were used to create the client part. MySQL was used to write the database. Further development is possible in the direction of improving the interface to create a more user-friendly interaction with the web application, improve server performance and add functions that the server can perform.
30
Bonnier, Victor. "Comparison between OpenStack virtual machines and Docker containers in regards to performance." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-19934.
Full textAbstract:
Cloud computing is a fast growing technology which more and more companies are starting to use throughout the years. When deploying a cloud computing application it is important to know what kind of technology that you should use. Two popular technologies are containers and virtual machines. The objective with this study was to find out how the performance differs between Docker containers and OpenStack virtual machines in regards to memory usage, CPU utilization, time to boot up and throughput from a scalability perspective when scaling between two and four instances of containers and virtual machines. The comparison was done by having two different virtual machines running, one with Docker that ran the containers and another machine with OpenStack that was running a stack of my virtual machines. To gather the data from the virtual machines I used the command ”htop” and to get the data from the containers, I used the command ”Docker stats”. The results from the experiment showed a favor towards the Docker containers where the boot time on the virtual machines were between 280-320 seconds and the containers had between 5-8 seconds bootup time. The memory usage was more than doubled on the virtual machines than the containers. The CPU utilization and throughput favored the containers and the gap in performance increased when scaling the application outwards to four instances in all cases except for the throughput when adding information to a database. The conclusion that can be drawn from this is that Docker containers are favored over the OpenStack virtual machines from a performance perspective. There are still other aspects to think about regarding when choosing which technology to use when deploying a cloud application, such as security for example.
31
Ahmed, Arif. "Efficient cloud application deployment in distributed fog infrastructures." Thesis, Rennes 1, 2020. http://www.theses.fr/2020REN1S004.
Full textAbstract:
Les architectures Fog computing sont composées d'un grand nombre de machines dispersées dans une zone géographique telle qu'une ville ou une région. Dans ce contexte il est important de permettre un démarrage rapide des applications déployées sous forme de containers Docker. Cette thèse étudie les raisons de la lenteur de déploiement, et identifie trois opportunités susceptibles de réduire le temps de déploiement des conteneurs: (1) améliorer le taux de réussite du cache Docker; (2) accélérer l'opération d'installation d'une image; et (3) accélérer le processus de démarrage après la création d'un conteneurFog computing architectures are composed of a large number of machines distributed across a geographical area such as a city or a region. In this context it is important to support a quick startup of applications deployed in the for of docker containers. This thesis explores the reasons for slow deployment and identifies three improvement opportunities: (1) improving the Docker cache hit rate; (2) speed-up the image installation operation; and (3) accelerate the application boot phase after the creation of a container
32
Ericson, Amanda. "Mitigating garbage collection in Java microservices : How garbage collection affects Java microservices andhow it can be handled." Thesis, Mittuniversitetet, Institutionen för informationssystem och –teknologi, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:miun:diva-42299.
Full textAbstract:
Java is one of the more recent programming languages that in runtime free applications from manual memory management by using automatic Garbage collector (GC) threads. Although, at the cost of stop-the-world pauses that pauses the whole application. Since the initial GC algorithms new collectors has been developed to improve the performance of Java applications. Still, memory related errors occurs and developers struggle to pick the correct GC for each specific case. Since the concept of microservices were established the benefits of using it over a monolith system has been brought to attention but there are still problems to solve, some associated to garbage collectors. In this study the performance of garbage collectors are evaluated and compared in a microservice environment. The measurements were conducted in a Java SpringBoot application using Docker and a docker compose file to simulate a microservice environment. The application outputted log files that were parsed into reports which were used as a basis for the analysis. The tests were conducted both with and without a database connection. Final evaluations show that one GC does not fit all application environments. ZGC and Shenandoah GC was proven to perform very good regarding lowering latency, although not being able to handle the a microservice environment as good as CMS. ZGC were not able to handle the database connection tests at all while CMS performed unexpectedly well. Finally, the study enlightens the importance of balancing between memory and hardware usage when choosing what GC to use for each specific case.
33
Pothuraju, Rohit. "Measuring and Modeling of Open vSwitch Performance : Implementation in KVM environment." Thesis, Blekinge Tekniska Högskola, Institutionen för kommunikationssystem, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13519.
Full textAbstract:
Network virtualization has become an important aspect of the Telecom industry. The need for efficient, scalable and reliable virtualized network functions is paramount to modern networking. Open vSwitch is a virtual switch that attempts to extend the usage of virtual switches to industry grade performance levels on heterogeneous platforms.The aim of the thesis is to give an insight into the working of Open vSwitch. To evaluate the performance of Open vSwitch in various virtualization scenarios such as KVM and Docker (from second companion thesis)[1]. To investigate different scheduling techniques offered by the Open vSwitch software and supported by the Linux kernel such as FIFO, SFQ, CODEL, FQCODEL, HTB and HFSC. To differentiate the performance of Open vSwitch in these scenarios and scheduling capacities and determine the best scenario for optimum performance.The methodology of the thesis involved a physical model of the system used for real-time experimentation as well as quantitative analysis. Quantitative analysis of obtained results paved the way for unbiased conclusions. Experimental analysis was required to measure metrics such as throughput, latency and jitter in order to grade the performance of Open vSwitch in the particular virtualization scenario.The result of this thesis must be considered in context with a second companion thesis[1]. Both the theses aim at measuring and modeling performance of Open vSwitch in NFV. However, the results of this thesis outline the performance of Open vSwitch and Linux bridge in KVM virtualization scenario. Various scheduling techniques were measured for network performance metrics and it was observed that Docker performed better in terms of throughput, latency and jitter. In the KVM scenario, from the throughput test it was observed that all algorithms perform similarly in terms of throughput, for both Open vSwitch and Linux bridges. In the round trip latency tests, it was seen that FIFO has the least round trip latency, CODEL and FQCODEL had the highest latencies. HTB and HFSC perform similarly in the latency test. In the jitter tests, it was seen that HTB and HFSC had highest average jitter measurements in UDP Stream test. CODEL and FQCODEL had the least jitter results for both Open vSwitch and Linux bridges.The conclusion of the thesis is that the virtualization layer on which Open vSwitch operates is one of the main factors in determining the switching performance. Docker performs better than KVM for both bridges. In the KVM scenario, irrespective of the scheduling algorithm considered, Open vSwitch performed better than Linux bridge. HTB had highest throughput and FIFO had least round trip latency. CODEL and FQCODEL are efficient scheduling algorithms with low jitter measurements.
34
Деркач, Б. О. "Веб-сервіси для контролю доступу до бібліографічної інформації." Thesis, Чернігів, 2021. http://ir.stu.cn.ua/123456789/24974.
Full textAbstract:
Деркач, Б. О. Веб-сервіси для контролю доступу до бібліографічної інформації : випускна кваліфікаційна робота : 123 "Комп’ютерна інженерія" / Б. О. Деркач ; керівник роботи О. А. Пріла ; НУ "Чернігівська політехніка", кафедра інформаційних і комп’ютерних систем. – Чернігів, 2021. – 81 с.Об’єктом розробки є створення серверу, архітектури БД та їх взаємодії. Для створення проекту використовувалося декілька технологій: nest.js – фреймворк для написання серверної частини, docker – для створення контейнеру БД, postgresql – БД та допоміжні бібліотеки. Метою даної роботи є: - Продемонструвати можливості даного стеку технологій для вирішення подібних питань. - Удосконалення володіння даними інструментами. За останні роки створення веб додатків та серверних частин дуже змінилося. З’явилося багато потужних інструментів які тісно конкурують між собою. В світі техніки спостерігається велика різноманітність пристроїв з яких користувачі можуть користуватися веб додатками. Разом з цим і користувачі використовують більше ресурсів і програмістам потрібно при написанні коду орієнтуватися на все більший масштаб технологій. Під час написання роботи були врахування такого розвитку технологій.
The object of development is the operation of the server for this purpose of the project. Several technologies were used to create the project: nest.js - a framework for writing the server part, docker - to create a database container, postgresql - a database and auxiliary libraries. The programs described above are the most popular in their field and in my opinion easy to use. The purpose of this work is: - Demonstrate the capabilities of this technology stack to address such issues. - Improving the mastery of these tools. In recent years, the creation of web applications and server parts has changed a lot. There are many powerful tools that compete closely with each other. In the world of technology there is a great variety of devices from which users can use web applications. At the same time, users are using more resources and programmers need to focus on a growing scale of technology when writing code. At the time of writing, such developments in technology have been taken into account.
35
Robinet, Gilles. "Conséquences de l'inhalation des poussières de soja sur la fonction respiratoire des dockers des ports de commerce de Brest et Lorient." Brest, 1989. http://www.theses.fr/1989BRES3067.
Full text
36
Fabbri, Enrico Maria. "Kubernetes e Doker vs Virtual Private Server." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2021.
Find full text
37
Zenk, Viktor, and Martin Malmström. "A comparative study of Docker and Vagrant regarding performance on machine level provisioning." Thesis, Tekniska Högskolan, Jönköping University, JTH, Datateknik och informatik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-49552.
Full textAbstract:
Software projects can nowadays have complex infrastructures behind them, in the form of libraries and various other dependencies which need to be installed on the machines they are being developed on. Setting up this infrastructure on a new machine manually can be a tedious process prone to errors. This can be avoided by automating the process using a software provisioning tool, which can automatically transfer infrastructure between machines based on instructions which can be version controlled in similar ways as the source code. Docker and Vagrant are two tools which can achieve this. Docker encapsulates projects into containers, while Vagrant handles automatic setup of virtual machines. This study compares Docker and Vagrant regarding their performance for machine level provisioning, both when setting up an infrastructure for the first time on a new machine, as well as when implementing a change in the infrastructure configuration. This was done by provisioning a project using both tools, and performing experiments measuring the time taken for each tool to perform the tasks. The results of the experiments were analyzed, and showed that Docker performed significantly better than Vagrant in both tests. However, due to limitations of the study, this cannot be assumed to be true for all use cases and scenarios, and performance is not the only factor to consider when choosing a provisioning tool. According to the data collected in this study, Docker is thereby the recommended tool to choose, but more research is needed to determine whether other test cases yield different results.Moderna mjukvaruprojekt kan ha en komplex infrastruktur bakom sig, i form av bibliotek och andra beroenden som måste installeras på utvecklarmaskiner. Att konfigurera denna infrastruktur på en ny maskin manuellt kan vara en tidskrävande process, som även kan leda till en ofullständigt eller felaktigt konfigurerad lösning. Detta kan undvikas genom att automatisera processen med hjälp av provisioneringsverktyg, som automatiskt kan överföra infrastrukturer mellan maskiner baserat på instruktioner som kan versionshanteras på liknande sätt som källkoden. Docker och Vagrant är två verktyg som kan användas till detta ändamål. Docker kapslar in projektet i containers, medan Vagrant hanterar automatisk konfiguration av virtuella maskiner. Denna studie jämför Docker och Vagrant avseende deras prestanda för mjukvaruprovisionering på maskinnivå, både när det kommer till en förstagångsinstallation av infrastrukturen på en ny maskin, och även implementering av en ändring i konfigurationen av infrastrukturen. Denna jämförelse gjordes genom att implementera båda lösningarna, och sedan utföra experiment för att mäta tidsåtgången för båda verktygen att lösa de två uppgifterna. Resultaten av experimenten analyserades, och visade att Docker presterade bättre än Vagrant i båda tester. På grund av begränsningar i studien kan detta inte antas vara sant för alla användningsområden och scenarier, och prestanda är inte den enda faktorn att ha i åtanke när ett provisioneringsverktyg ska väljas. Baserat på datan insamlad i denna studie är Docker därmed verktyget som rekommenderas, men mer forskning krävs för att avgöra om andra testområden ger andra resultat.
38
Gerber, Lorenz. "Containerization for HPC in the Cloud: Docker vs Singularity - A Comparative Performance Benchmark." Thesis, Umeå universitet, Institutionen för datavetenskap, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-155291.
Full textAbstract:
In recent years, ‘containerization’, also known as ‘light-weight virtualization’, has arguably been one of the dominating buzzwords, both in industry and academic research. While scalability has been the main drivingforce in industry, reproducibility is often stated as the main benefit of containers in scientific High Performance Computing (HPC). Docker is currently the most widely deployed framework, ideally suited for microservice architecture. Singularity is a framework that aims to provide mobility of compute with a focus on bare-metal HPC cluster systems. In earlier studies the performance of different light-weight virtualization frameworks when deployed on bare metal HPC systems has been evaluated and Singularity was mostly found to be superior to others in it’s application niche. However, performing HPC applications in the cloud has recently become a viable alternative to dedicated bare-metal HPC clusters. This results in running light-weight virtualization frameworks on virtual machines. The aim of this study was to benchmark the performance of Singularity when run on virtual machines in the cloud compared to a setup using’Docker’. Adhering to earlier studies, performance metrics for compute, I/O, memory, and network through put/latency were established.
39
Івасюк, Д. В. "Розробка сайту ВСП ФКТКТ НУ "ЧП" з електронним журналом користувачів (back - end)." Thesis, Чернігів, 2021. http://ir.stu.cn.ua/123456789/23031.
Full textAbstract:
Івасюк, Д. В. Розробка сайту ВСП ФКТКТ НУ "ЧП" з електронним журналом користувачів (back - end) : випускна кваліфікаційна робота : 123 "Кoмп’ютepнa iнжeнepiя" / Д. В. Івасюк ; керівник роботи С. С. Стасюк ; НУ "Чернігівська політехніка", кафедра iнфopмaцiйниx тa кoмп’ютepниx cиcтeм. – Чернігів, 2021. – 57 с.Метою теоретичної частити є вивчення існуючих технологій для реалізації back-end сайту.
he purpose of the theoretical part is to study the existing technologies for the implementation of the back-end site.
40
Volpe, Alessio. "Virtual Distributed Container." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2018. http://amslaurea.unibo.it/16748/.
Full textAbstract:
Nell'ambito che vede protagonisti i container per la realizzazione di applicazioni distribuite Virtual Distributed Container (VDC) offre un nuovo modello di rete.
Questo lavoro ha l'obiettivo di fornire il supporto delle reti VDE ai container Docker. VDC è implementato sotto forma di plugin installabile all'interno di Docker.
41
Friðriksson, Vilhelm. "Container overhead in microservice systems." Thesis, KTH, Radio Systems Laboratory (RS Lab), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-235693.
Full textAbstract:
Containers have been gaining popularity in recent years due to their ability to provide higher flexibility, higher reliability and dynamic scalability to enterprise software systems. In order to fully utilize containers, software developers aim to build their software using microservice architecture, meaning that instead of working on a single large codebase for the whole project, the software is split into smaller units. These microservices can be deployed in their own container instead of the traditional virtual machine setup where a server has to configured with all necessary dependencies. Moving away from the monolithic software architecture to containerized microservices is bound to bring performance penalties due to increased network calls between services and container overhead. The integration must therefor be carefully planned in order to fully utilize the container setup while minimizing the overhead. The purpose of this thesis project was to measure how much overhead can be expected due to containers in an enterprise environment. By using a combination of virtual machines and Docker containers, a microservice system was deployed with four different deployment strategies and the system’s performance was measured by analyzing request response times under various loads. The services were made to run on a single server and on multiple servers, with and without Docker. The performance measurements showed that the system performed worse in every case when Docker was used. Furthermore, the results showed that Docker can have significant negative impact on performance when there is a heavy load on the system.Containers har blivit populärare under de senaste åren tack vare deras förmåga att ge högre flexibilitet, högre tillförlitlighet och dynamisk skalbarhet för företagsprogramvarusystem. För att fullt ut kunna använda containers har programutvecklarna för avsikt att bygga sin programvara med hjälp av mikroservicearkitekturen, vilket innebär att programvaran delas upp i mindre enheter istället för att arbeta på en enda stor kodbas för hela projektet. Dessa mikroservices kan distribueras i sina egna containers istället för den traditionella virtuella maskininstallationen, där en server måste konfigureras med alla nödvändiga beroenden. Att flytta sig från monolitisk mjukvaruarkitektur till containeriserade microservices kommer att få prestandaförsämringar på grund av ökade nätverksanrop mellan tjänster och container-overhead. Integrationen måste därför noggrant planeras för att fullt ut utnyttja containeruppsättningen och minimera overhead. Syftet med detta avhandlingsprojekt var att mäta hur mycket overhead kan förväntas på grund av containers i en företagsmiljö. Genom att använda en kombination av virtuella maskiner och Dockercontainers, implementerades ett microservices-system med fyra olika implementeringsstrategier och systemets prestanda mättes genom att analysera anropens svarstid under olika belastningar. Tjänsterna gjordes för att köras på en enda server och på flera servrar, med och utan Docker. Prestandamätningarna visade att systemet var sämre i alla fall när Docker användes. Dessutom, visade resultaten att Docker kan ha signifikant negativ inverkan på prestanda när det är tung belastning på systemet.
42
Сослуєв, О. В. "Інформаційний чат-бот COVID-19 для месенджера Telegram." Thesis, Чернігів, 2021. http://ir.stu.cn.ua/123456789/24978.
Full textAbstract:
Сослуєв, О. В. Інформаційний чат-бот COVID-19 для месенджера Telegram : випускна кваліфікаційна робота : 123 "Комп’ютерна інженерія" / О. В. Сослуєв ; керівник роботи А. І. Роговенко ; НУ "Чернігівська політехніка", кафедра інформаційних і комп’ютерних систем. – Чернігів, 2021. – 93 с.Дипломна робота має полягає в написанні інформаційного чат-бота для мсенджера Telegram про Covid-19. Чат-бот–це комп’ютерна програма, основним призначеням якої є обмін інформацією з користувачем за попередньо визначеним алгоритмом або за допомогою штучного інтелекту. Telegram – це додаток, розроблений на мові програмування C ++, що дозволяє обмінюватися повідомленнями і файлами більшості форматів. Месенджер використовує спеціально розроблену серверну частину з закритим кодом, які працюють на серверах Німеччини і США. Метою роботи є: -Проєктуваня логіки чат-боту та розміщення в ньому інформації -Розробка чат-боту -Використання бази даних -Розміщеня на серврі Головна мета цього проєкту інформування коримтувачів про Covid-19 в одному місці, а саме в Telegram. Це більш зручно чим дівитися на різних сайтів. Проєкт буду розміщений на відаленому сервері Heroku, що дає можливість роботи боту 24 години на добу.
The subject of the thesis is to write the information chatbot for the Telegram messenger about Covid-19. Chatbot is a computer program whose main purpose is to exchange information with the user according to a predetermined algorithm or using artificial intelligence. Telegram is an application developed in the C ++ programming language that allows you to exchange messages and files in most formats. Messenger uses a specially designed closed source server part that runs on servers in Germany and the United States. The purpose of the work is: - Designing the logic of the chatbot and placing information in it -Development of a chat bot -Using a database -Post on the server The main goal of this project is to inform users about Covid-19 in one place, namely in Telegram. This is more convenient than looking at different sites. The project will be hosted on a remote Heroku server, which allows the bot to work 24 hours a day.
43
Rubak, Adam, and Joakim Wennerblom. "Prototyp för MS SQL-testning i Dockermiljö." Thesis, Karlstads universitet, Institutionen för matematik och datavetenskap (from 2013), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kau:diva-84521.
Full textAbstract:
Att utveckla applikationer kräver mer än kod. Docker förenklar och accelererar utveckling av mjukvara, samtidigt som det ger utvecklare friheten att använda sig av olika verktyg, metoder och publiceringsmiljöer. Prevas utvecklar idag många system som använder sig av MS SQL Server och .NET i Docker men saknar ett smidigt sätt att testa systemen innan leverans. Målet med projektet är att skapa en prototyp åt Prevas i Karlstad som gör det möjligt att smidigt testa och säkerställa förväntad funktionalitet hos MS SQL-serverbaserade applikationer. Resultatet av projektet är ett program som gör det möjligt att testa kommunikationen mellan en MS SQL Server och en applikation, samt presentera resultatet för användaren i en webbklient. Vår prototyp visar att det är möjligt att utveckla ett sådant system. Dock finns det delar av systemet som behöver utredas t.ex. nedladdning av testresultat, robust felhantering, samt att utveckla den till en mer generell lösning som går att anpassa efter databasens struktur.Application development requires more than skills in writing good code. Tools like Docker can accelerate the development of software and it gives the developer the freedom to change the tools, methods, and deployment environments. Prevas is developing systems that use MS SQL Servers and .NET environments in Docker but they need to make it more effective by automating the process of testing the database before deployment. The goal of this project is to create a prototype for Prevas that makes it possible to easily test and ensure expected functionality of MS SQL Server based applications. The result of the project is a program that makes it possible to test the communication between a database and an application as well as present the outcome in a web client for the user. Our prototype shows that the development of similar systems is possible but there are pieces of the system that needs further development. Some examples include downloading the results of the tests, robust error handling methods, as well developing a more general application to adapt the system to a database structure.
44
Zhang, Wenhui. "Design and Implementation of SQL Online Practice Platform." TopSCHOLAR®, 2019. https://digitalcommons.wku.edu/theses/3091.
Full textAbstract:
Database management is a very important subject in computer science education. The study of SQL syntax is the most important part of this course. The traditional teaching method only lets the students practice SQL syntax through the textbook exercise. Students cannot get the query result directly. Moreover, students do not know intuitively what is wrong with the query sentence. In this study, we want to find a better way for the teachers and the students to learn this part of database management. Teacher uploads a SQL file through a web page, it will create a database with several tables and some data records on the database server. The student logs in to the platform and chooses the database that he wants to practice. The student can do all regular database management operations such as query data, insert data, delete data, etc. If the query sentence is correct, the query result will be displayed on the webpage. If not, the detailed error information will show up. Since there is more than one student using the platform, so these operations cannot change the database created by the teacher. Therefore, the student’s process will run in a Docker container. In the container, there is a duplicated database of the teacher’s database. Meanwhile, the platform supports multiple users to do exercise with one database at the same time.
45
Kokkalis, Andreas. "On-demand virtual laboratory environments for Internetworking e-learning : A first step using docker containers." Thesis, KTH, Kommunikationssystem, CoS, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-222010.
Full textAbstract:
Learning Management Systems (LMSs) are widely used in higher education to improve the learning, teaching, and administrative tasks for both students and instructors. Such systems enrich the educational experience by integrating a wide range of services, such as on-demand course material and training, thus empowering students to achieve their learning outcomes at their own pace. Courses in various sub-fields of Computer Science that seek to provide rich electronic learning (e-learning) experience depend on exercise material being offered in the forms of quizzes, programming exercises, laboratories, simulations, etc. Providing hands on experience in courses such as Internetworking could be facilitated by providing laboratory exercises based on virtual machine environments where the student studies the performance of different internet protocols under different conditions (such as different throughput bounds, error rates, and patterns of changes in these conditions). Unfortunately, the integration of such exercises and their tailored virtual environments is not yet very popular in LMSs. This thesis project investigates the generation of on-demand virtual exercise environments using cloud infrastructures and integration with an LMS to provide a rich e-learning in an Internetworking course. The software deliverable of this project enables instructors to dynamically instantiate virtual laboratories without incurring the overhead of running and maintaining their own physical infrastructure. This sets the foundations for a virtual classroom that can scale in response to higher system utilization during specific periods of the academic calendar.Lärplattformar (eng. Learning Management Systems (LMS)) används i stor utsträckning för högre utbildning för att förbättra lärande, undervisning och administrativa uppgifter för både studenter och instruktörer. Sådana system berikar den pedagogiska erfarenheten genom att integrera ett brett utbud av tjänster, såsom on-demand kursmaterial och träning, vilket ger studenterna möjlighet att uppnå sina lärandemål i egen takt. Kurser inom olika delområden av datavetenskap som syftar till att ge en bred erfarenhet av elektroniskt lärande (e-learning) har träningsmaterial i form av frågesporter, programmeringsövningar, laboratorier, simuleringar etc. Praktiskt erfarenhet i kurser som Internetworking kan underlättas genom att tillhandahålla laboratorieövningar baserade på virtuella maskinmiljöer där studenten studerar prestanda för olika internetprotokoll under olika förhållanden (t.ex. olika gränsvärden, felfrekvenser och förändringsmönster under dessa förhållanden). Tyvärr är integrationen av sådana övningar och deras skräddarsydda virtuella miljöer ännu inte populär i LMSs. Detta examensarbete undersöker generering av virtuella träningsmiljöer på begäran med hjälp av molninfrastruktur och integration med en LMS för att ge ett rikt e-lärande i en Internetworking-kurs. Programvaran som levereras av detta projekt gör det möjligt för instruktörer att dynamiskt instansera virtuella laboratorier utan att behöva hantera sin egen fysiska infrastruktur. Detta sätter grunden för ett virtuellt klassrum som kan skala med högre systemutnyttjande under specifika perioder av den akademiska kalendern.
46
Tyresson, Dennis. "Security implications for docker container environments deploying images from public repositories : A systematic literature review." Thesis, Högskolan i Skövde, Institutionen för informationsteknologi, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:his:diva-18977.
Full textAbstract:
Because of the ease of use and effectiveness, Docker containers have become immensely popular among system administrators worldwide. Docker elegantly packages entire applications within a single software entity called images, allowing fast and consistent deployment over different host systems. However, it is not without drawbacks, as the close interaction with the operating system kernel gives rise to security concerns. The conducted systematic literature review aims to address concerns regarding the use of images from unknown sources. Multiple search terms were applied to a set of four scientific databases in order to find peer-reviewed articles that fulfill certain selection criteria. A final amount of 13 articles were selected and evaluated by using means of thematic coding. Analysis showed that users need to be wary of what images are used to deploy containers, as they might contain malicious code or other weaknesses. The use of automatic vulnerability detection using static and dynamic detection could help protect the user from bad images.
47
Oumaziz, Mohamed Ameziane. "Cloning beyond source code : a study of the practices in API documentation and infrastructure as code." Thesis, Bordeaux, 2020. http://www.theses.fr/2020BORD0007.
Full textAbstract:
Lors du développement de logiciels, la maintenance et l'évolution constituent une partie importante du cycle de vie du développement représentant 80% du coût et des efforts globaux.Au cours de la maintenance, il arrive que les développeurs aient copier-coller des fragments de code source afin de les réutiliser. Une telle pratique, apparemment inoffensive, est plus fréquente qu'on ne le pense.Communément appelés «clones» dans la littérature, ces doublons de code source sont un sujet bien connu et étudié en génie logiciel.Dans cette thèse, nous visons à mettre en lumière les pratiques du copier-coller sur les artefacts logiciels.En particulier, nous avons choisi de concentrer nos contributions sur deux types d'artefacts logiciels : Documentation d'API et fichiers de compilation (c.-à-d. Dockerfiles). Pour les deux contributions, nous suivons une méthodologie d'étude empirique commune.Tout d'abord, nous montrons que les documentations d'API et les fichiers de construction de logiciels (c.-à-d. Dockerfiles) sont confrontés à des problèmes de doublons et que de tels doublons sont fréquents.Deuxièmement, nous identifions les raisons derrière l'existence de ces doublons.Troisièmement, nous effectuons une enquête auprès de développeurs expérimentés et de constatons qu'ils sont conscients de ces doublons, et qu'ils les rencontrent souvent tout en ayant un avis mitigé sur eux.Enfin, nous montrons que les deux artefacts logiciels manquent de mécanismes de réutilisation pour faire face aux doublons, et que certains développeurs ont même recours à des outils ad-hoc pour les gérerWhen developing a software, maintenance and evolution represents an important part of the development's life-cycle, making up to 80% of the overall cost and effort.During the maintenance effort, it happens that developers have to resort to copying and pasting source code fragments in order to reuse them.Such practice, seemingly harmless is more frequent than we expect.Commonly referred to as ``clones'' in the literature, these source code duplicates are a well-known and studied topic in software engineering.In this thesis, we aim at shedding some light on copy-paste practices on software artifacts. In particular, we chose to focus our contributions on two specific types of software artifacts: API documentation and build files (i.e. Dockerfiles).For both contributions, we follow a common empirical study methodology. First, We show that API documentations and software build files (i.e. Dockerfiles) actually face duplicates issues and that such duplicates are frequent.Secondly, we identify the reasons behind the existence of such duplicates.Thirdly, We perform a survey on experimented developers and find that they're aware of such duplicates, frequently face them. But still have a mixed opinion regarding them.Finally, We show that both software artifacts lack reuse mechanisms to cope with duplicates, and that some developers even resort to ad-hoc tools to manage them
48
Flygare, Robin, and Anthon Holmqvist. "Performance characteristics between monolithic and microservice-based systems." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-14888.
Full textAbstract:
A new promising technology to face the problem of scalability and availability is the microservice architecture. The problem with this architecture is that there is no significant study that clearly proves the performance differences compared to the monolithic architecture. Our thesis aims to provide a more conclusive answer of how the microservice architecture differs performance wise compared to the monolithic architecture. In this study, we conducted several experiments on a self-developed microservice and monolithic system. We used JMeter to simulate users and after running the tests we looked at the latency, successful throughput for the tests and measured the RAM and CPU usage with Datadog. Results that were found, were that the microservice architecture can be more beneficial than the monolithic architecture. Docker was also proven to not have any negative impact on performance and computer cluster can improve performance. We have presented a conclusive answer that microservices can be better in some cases than a monolithic architecture.
49
Olle, Emilsson, and Hrvatin Marcus. "Using containers in a continuous integration and delivery environment : A performance and scalability comparison." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-16662.
Full textAbstract:
With a software industry that is moving at a fast pace, continuous integration and delivery is something important for many products today. Moreover, with containers being on the rise since 2013, more companies are moving their CI/CD environment into containers not only for development but also for testing. This thesis begins with giving the reader an introduction to containers, container orchestration, and Jenkins, which is a continuous integration and delivery tool. The experiment was then set up with one container based cluster and one single node machine. Two kinds of experiments were run on them, one big job and one small job. The system scalability is assessed, and with smaller clusters the memory overhead could be an issue. Performance wise, the container cluster is performing better than a single node machine, as long as it is utilizing all its nodes. Security with containers is still an issue and it could be fatal for a cluster if it is compromised.
50
Szymeczek, Andrzej. "Vytvoření simulačního modelu přístupové sítě." Master's thesis, Vysoké učení technické v Brně. Fakulta elektrotechniky a komunikačních technologií, 2020. http://www.nusl.cz/ntk/nusl-413103.
Full textAbstract:
The topic of the diploma thesis is " Application of simulation model of access network". The aim of the thesis was to create a part of the access network in which were tested simulations for TCP and UDP traffic. The theoretical part of the thesis deals with general information about the GNS3 program and the possibilities which this program allows. The next part of the thesis describes the Mikrotik RouterOS program, which was used in the topology. The next section describes the types of routing in IP networks, as well as the types of packet delivery. The practical part deals with the creation of test topologies and verification of the performance of the simulation tool. Furthermore, the practical part deals with the programming of a network generator for TCP and UDP traffic in the network. The generator was created by using a Bash script and a combination of the dd and nc commands. At the end, the thesis describes the results of simulations in terms of transmission speed, network throughput, packet size distribution and in the case of TCP also bidirectional delay – RTT.