The exam will consist of:

• creating a web application deployment to the public cloud.
• uploading related files to GIT before the exam date.
• answering two or three questions about what you uploaded and what was discussed in the lecture.

Web Application Deployment

During the exam, you will present a web application deployed to the public cloud environment of your choice.

You may (but do not have to) use the same web application that you used during the first or second assignment.

The application should meet the following conditions:

• it should be publicly accessible using a web browser and the HTTPS protocol at least at the time of the exam.
• a functional HTTPS certificate should be issued and configured for the URL.
• application deployment should be repeatable using scripts and configuration files, application deployment to the cloud should not require interaction with the web interface.
• the application should consist of at least three containers or other components.
• the application should be easy to terminate using a script.
• the application should use a persistent volume, data store or database.
• the application should restart automatically in case of an error.
• you should be able to back up the application.
• the application should be configurable using files or environment variables.
• Secrets should be configurable using environment variables and should not be in GIT.
• you should be able to view access logs from the internet.

Upload to GIT

Upload the related files to GIT to the sk1 directory similarly to the assignments.

• prepare-app.sh: script for preparing the application and creating all related services.
• remove-app.sh: remove the application and all related services.
• All necessary files to run prepare-app.sh, source files, configurations, e.g. Dockerfile, sql scripts, etc.
• Documentation file README.md.

In the documentation file, include:

• Description of what your application does.
• Verbal description of the public cloud used, cloud services, Kubernetes or Docker objects, persistent volumes, databases that you have used.
• Analysis of the costs for one year of operation of your application in the event that the estimated number of users is 1000 per day and the size of the files or database is 50GB. In the analysis, include the cloud resources you need, their price and billing interval.
• Description of the files you have uploaded and their content.
• Brief description of the written configuration.
• Instructions on how to view and use the application on the web browser.
• Instructions on how to perform a data backup.
• Instructions on how to view access records from the Internet.
• Conditions under which it is possible to run the prepare-app.sh and remove-app.sh scripts.
• List of external resources for developing, type and method of using the generative model

Defense

The defense process takes a total of max. 7 min.:

1. Presentation of your application - what it can do and who it is intended for. The application should be publicly accessible on the day of the exam.
2. Technical details of your solution: Kubernetes objects, Docker application containers or public cloud services that you used, the method of communication of individual application components - frontend, backend, database. Workflow when creating an application deployment to the public cloud.
3. Answering two or three questions. The questions will be about what you submitted and what was said in the lectures.

Evaluation

Maximum 70 points.

What was submitted, how it was presented and how the questions were answered will be evaluated.

Full evaluation will be given to:

• A working, useful, consistently prepared and correctly deployed application.
• Edited, readable and concise documentation.
• A prompt and correct answer to the questions asked.

Penalization will be given to:

• Poorly defined personal contribution.
• Low originality of the application - generic web application (wordpress, mysqladmin, pgadmin, etc.).
• A non-functioning certificate.
• Incomplete documentation.
• Technical errors in the application.
• Configuration in source files, not in configuration files.
• Bad-looking application or bad-looking documentation.
• Missing scripts or configuration files.

Previous Post