Skip to content

vivoit00/PuVS-to-do-list

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

9 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

2024-March-11 Cloud and Semester Introduction

Initial Brainstorming Session - Technologies and Motivators for Distributed Systems

Brainstorming

Content

  • Why distributed systems, why container, why modern software?
  • What is Cloud Computing? Encounters in everyday life and history
  • Characteristic, advantages & challenges
  • Terminology - public, private, hybrid, dedicated
  • Abstraction layers - IaaS, PaaS, FaaS, SaaS
  • Overview - Hypervisors, virtual machines, containers and orchestration

Objectives and exercises

The student is able to describe the reasons for distributed systems and cloud computing in own words and list examples for offerings, topologies and technologies. Includes ability to differentiate between different abstraction layers and knowledge how those layers and according technologies interact with each other. No exercises in this module

Student Questions

  • What is Polyglot Software Development?
  • What did the role of containers change for polyglot software?
  • Security and Cloud - is it safe? :-)

Polyglot Container

Outlook for Labs

  • Distributed app
  • Polyglot implementation
  • Containerisation
  • Kubernetes
  • DevOps/CICD/Observability (optional)

Exercise Tech Stack

Homework

  • Get a public GitHub, GitLab or Bitbucket account
  • Play around with GitHub codespaces and/or Gitpod

2024-March-18 Session canceled

2024-March-25 Cloud-based IDEs Intro & Docker/Container

Content

  • Why do we need Containers?

  • Challenges for (polyglot) distributed systems in traditional IT:

    • Each environment has to be configured manually: Servers as well as local dev environments
    • Configuration has to be as identical as possible: minor configuration drifts can lead to errors and the "it runs on my machine" problem
    • Polyglot Server Environments are a huge challenge as for each programing language a separate configuration has to be managed on all systems.
    • Changing Versions is tedious for local dev environment

    image

    • Whereas containerized Applications bring their own Environment and Configuration
    • No need to preconfigure the local environment per programming language or application.
    • Only the container engine is required to run all kinds of containers.

image

  • How does the container engine work?
  • Layer-based setup of containers
  • Container vs Container Image
  • How to create a container from application to dockerfile to image to running container

image

Student Questions:

  • Do I have to set up, build, and run the dockerfile for each container?
  • Can I run multiple applications inside a container?

Labs

Exercises can be found here

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages