Add more about containers vs vms
This commit is contained in:
43
slides.md
43
slides.md
@ -89,6 +89,7 @@ Here is another comment.
|
||||
|
||||
---
|
||||
transition: slide-up
|
||||
layout: quote
|
||||
level: 2
|
||||
---
|
||||
|
||||
@ -107,7 +108,7 @@ layoutClass: gap-16
|
||||
|
||||
# Problems?
|
||||
|
||||
- 📝 **It works on my machine?!?!** - Code behaves differently in development, testing, and production due to differences in environment (OS, dependencies, configurations).
|
||||
- 📝 **It works on my machine?!?!** - Code behaves differently in dev, testing, and production due to differences in environment (OS, dependencies, configurations).
|
||||
- 🎨 **Dependency conflicts** - Different applications require conflicting versions of the same dependency (e.g., Python 2 vs 3, different Node versions).
|
||||
- 🧑💻 **Slow and error-prone deployments** - Traditional deployments involve manual steps or configuration drift between environments.
|
||||
|
||||
@ -135,5 +136,45 @@ layoutClass: gap-16
|
||||
- Containers share the host OS kernel and are more lightweight, enabling faster startup and denser packing of applications.
|
||||
- Containers integrate well with orchestrators (like Kubernetes), enabling automated scaling, rolling updates, and fault tolerance.
|
||||
- Containers standardize development environments using tools like Docker Compose or dev containers.
|
||||
|
||||
|
||||
---
|
||||
transition: fade-out
|
||||
layout: two-cols-header
|
||||
title: Differences between VM and Container?
|
||||
---
|
||||
|
||||
# Differences between VM and Containers?
|
||||
|
||||
::left::
|
||||
## Virtual Machine
|
||||
- Virtualizes hardware
|
||||
- Runs a full guest OS (e.g., Linux or Windows)
|
||||
- Heavier: includes the OS, libraries, and application
|
||||
- Slow to start, uses more resources
|
||||
|
||||
**Example**: Running Ubuntu with Apache inside a VM on a Windows host
|
||||
|
||||
::right::
|
||||
|
||||
## Container
|
||||
- Virtualizes at the OS level
|
||||
- Shares the host OS kernel
|
||||
- Isolates *only the application and its dependencies*
|
||||
- Lightweight: faster startup, lower resource use
|
||||
|
||||
**Example:** Running a Node.js app in a container using the host's Linux kernel
|
||||
|
||||
|
||||
---
|
||||
transition: fade-out
|
||||
---
|
||||
|
||||
# How do they work?
|
||||
|
||||
|
||||
## Containers are just processes
|
||||
|
||||
If you don't take anything else away from this talk, I hope you walk away with a better understanding of this fundamental. As far as the OS is concerned, a container is just another process/set of processes to the operating system.
|
||||
---
|
||||
|
||||
|
Reference in New Issue
Block a user