Zero-Downtime Deployment in a High Availability Architecture : Controlled experiment of deployment automation in a high availability architecture

Computer applications are no longer local installations on our computers. Many modern web applications and services rely on an internet connection to a centralized server to access the full functionality of the application. High availability architectures can be used to provide redundancy in case of...

Full description

Bibliographic Details
Main Author: Nilsson, Axel
Format: Others
Language:English
Published: Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM) 2018
Subjects:
Online Access:http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-74971
id ndltd-UPSALLA1-oai-DiVA.org-lnu-74971
record_format oai_dc
spelling ndltd-UPSALLA1-oai-DiVA.org-lnu-749712018-06-06T05:22:33ZZero-Downtime Deployment in a High Availability Architecture : Controlled experiment of deployment automation in a high availability architectureengNilsson, AxelLinnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM)2018High AvailabilityZero-Downtime DeploymentContinuous DeploymentAutomationComputer SystemsDatorsystemComputer applications are no longer local installations on our computers. Many modern web applications and services rely on an internet connection to a centralized server to access the full functionality of the application. High availability architectures can be used to provide redundancy in case of failure to ensure customers always have access to the server. Due to the complexity of such systems and the need for stability, deployments are often avoided and new features and bug fixes cannot be delivered to the end user quickly. In this project, an automation system is proposed to allow for deployments to a high availability architecture while ensuring high availability. The purposed automation system is then tested in a controlled experiment to see if it can deliver what it promises. During low amounts of traffic, the deployment system showed it could make a deployment with a statistically insignificant change in error rate when compared to normal operations. Similar results were found during medium to high levels of traffic for successful deployments, but if the system had to recover from a failed deployment there was an increase in errors. However, the response time during the experiment showed that the system had a significant effect on the response time of the web application resulting in the availability being compromised in certain situations. Student thesisinfo:eu-repo/semantics/bachelorThesistexthttp://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-74971application/pdfinfo:eu-repo/semantics/openAccess
collection NDLTD
language English
format Others
sources NDLTD
topic High Availability
Zero-Downtime Deployment
Continuous Deployment
Automation
Computer Systems
Datorsystem
spellingShingle High Availability
Zero-Downtime Deployment
Continuous Deployment
Automation
Computer Systems
Datorsystem
Nilsson, Axel
Zero-Downtime Deployment in a High Availability Architecture : Controlled experiment of deployment automation in a high availability architecture
description Computer applications are no longer local installations on our computers. Many modern web applications and services rely on an internet connection to a centralized server to access the full functionality of the application. High availability architectures can be used to provide redundancy in case of failure to ensure customers always have access to the server. Due to the complexity of such systems and the need for stability, deployments are often avoided and new features and bug fixes cannot be delivered to the end user quickly. In this project, an automation system is proposed to allow for deployments to a high availability architecture while ensuring high availability. The purposed automation system is then tested in a controlled experiment to see if it can deliver what it promises. During low amounts of traffic, the deployment system showed it could make a deployment with a statistically insignificant change in error rate when compared to normal operations. Similar results were found during medium to high levels of traffic for successful deployments, but if the system had to recover from a failed deployment there was an increase in errors. However, the response time during the experiment showed that the system had a significant effect on the response time of the web application resulting in the availability being compromised in certain situations.
author Nilsson, Axel
author_facet Nilsson, Axel
author_sort Nilsson, Axel
title Zero-Downtime Deployment in a High Availability Architecture : Controlled experiment of deployment automation in a high availability architecture
title_short Zero-Downtime Deployment in a High Availability Architecture : Controlled experiment of deployment automation in a high availability architecture
title_full Zero-Downtime Deployment in a High Availability Architecture : Controlled experiment of deployment automation in a high availability architecture
title_fullStr Zero-Downtime Deployment in a High Availability Architecture : Controlled experiment of deployment automation in a high availability architecture
title_full_unstemmed Zero-Downtime Deployment in a High Availability Architecture : Controlled experiment of deployment automation in a high availability architecture
title_sort zero-downtime deployment in a high availability architecture : controlled experiment of deployment automation in a high availability architecture
publisher Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM)
publishDate 2018
url http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-74971
work_keys_str_mv AT nilssonaxel zerodowntimedeploymentinahighavailabilityarchitecturecontrolledexperimentofdeploymentautomationinahighavailabilityarchitecture
_version_ 1718691197940137984