Benefits of using cloud:

•  time to market
•  TCO
• self-sercvice dev/qa/pre envs
• automated scale up/down

The big three

AWS
Google [https://googlecloudcheatsheet.withgoogle.com/] Azure

X As a Service

Infrastructure: IaaS
Software: SaaS
Platform: PaaS
Kubernetes: KaaS

Why use a hosted Database?

Different ways to run a backend/frontend

“oldscool” – full IaaS
start a VM with ubuntu
ssh into VM (ansible, terraform)
install software (node,java,mysql…)
install app (from source?, from repo?)
VM + SaaS
use prebuilt images (packer, cloud specific)
configuration from (cloud-init, external source, git)
Containerized:
single VM (docker, compose, swarm)
cluster (swarm, k8s, cloud specific ecs?)
full GitOps

Containerization:

VM vs Containers
single Machine/Cluster
Orchestrators:
swarm
k8s
cloud specific:
AWS ECS
Azure: [https://azure.microsoft.com/en-us/products/category/containers/] registries (public/private, cloudself hosted)
vulnerability checking

CloudNative

Landscape [https://landscape.cncf.io/]

CI/CD (automation, automation, automation)

CI: every new git commit ⇒ new artifact
CD: every new artifact ⇒ deployed to qa/preprod/prod
The importance of tool choice
duck tape together legacy tools (jenkins + …)
modern Version Control Systems have integrated solutions:
gitlab
github-actions
on k8s you can DIY

DevOps, GitOps

DevOps: Pratices that combine development and IT operation to aim: short development life cycle, to provide continuous delivery.
GitOps: state of deployment (yaml/code) configuration is version controlled. Git is the one and only source of truth. Both the application and the infrastructure are now versioned artifacts and can be audited.[https://www.gitops.tech/] [https://about.gitlab.com/topics/gitops/] [https://www.weave.works/technologies/gitops/]

Serverless

Idea: for small projects, Proof of Concepts, Low traffic microservices, I don’t want to pay 24/7. Pay by time used (billed in millisec)