An application with Docker and Amazon Web Services
Nguyen, Duc (2019)
2019
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2019120424536
https://urn.fi/URN:NBN:fi:amk-2019120424536
Tiivistelmä
The main purpose of this thesis is to broaden the selection of cloud services by suggesting a guideline that can be utilized to deploy application on Amazon Web Services. The reason behind the decision to choose AWS Batch over AWS Lambda and other services are discussed. The author’s case company, Tori has been using AWS Batch to process high volumes of data in batch. Thus, the application must be scalable, resilient, nimble, and able to undertake heavy load.
Additionally, this thesis serves to demonstrate the steps needed to deploy an application using AWS and Docker, which are modern technologies and commonly used when developing software nowadays. The release pipeline in this project has been made in order to meet the demands of modern software development and improve the efficiency as well as robustness for the developers.
The result of this project is a fully functional software that plays an essential role in the case company and processes significant amount of data every day. The requirements for the software, such as elasticity, consistency, etc., are satisfied. Further improvements are planned and will be implemented in the nearest future.
Additionally, this thesis serves to demonstrate the steps needed to deploy an application using AWS and Docker, which are modern technologies and commonly used when developing software nowadays. The release pipeline in this project has been made in order to meet the demands of modern software development and improve the efficiency as well as robustness for the developers.
The result of this project is a fully functional software that plays an essential role in the case company and processes significant amount of data every day. The requirements for the software, such as elasticity, consistency, etc., are satisfied. Further improvements are planned and will be implemented in the nearest future.