Deployment Terminology
Deployment Types Hierarchy
Section titled “Deployment Types Hierarchy”Deployment Types│├── Bare Metal / Native│ ├── Physical Server│ ├── VPS (Virtual Private Server)│ └── Dedicated Server│├── Virtualized│ ├── Virtual Machines (VM)│ └── Hypervisor-based│├── Containerized│ ├── Docker│ ├── Kubernetes│ └── Container Orchestration│├── Serverless / FaaS│ ├── AWS Lambda│ ├── Vercel Functions│ └── Cloudflare Workers│└── Static Hosting / JAMstack ├── GitHub Pages ├── Vercel └── NetlifyTerm Definitions
Section titled “Term Definitions”Bare Metal / Native
Section titled “Bare Metal / Native”Physical Server → OS → ApplicationDeploy langsung di server tanpa kontainer/virtualisasi. Full control, no overhead.
Containerized
Section titled “Containerized”Physical Server → OS → Container Runtime → Container → ApplicationDeploy dalam container (Docker, Podman). Isolated, portable, scalable.
Static Hosting / JAMstack
Section titled “Static Hosting / JAMstack”CDN → Static Files → BrowserDeploy sebagai static files tanpa server-side processing. Auto-scaling, free tier.
Correct Usage
Section titled “Correct Usage”| ❌ Incorrect | ✅ Correct |
|---|---|
| ”Deploy di host langsung" | "Bare metal deployment" |
| "Deploy tanpa Docker" | "Native deployment" |
| "Deploy biasa" | "Self-hosted deployment” |
SnapCode Supports
Section titled “SnapCode Supports”| Type | Method | Command |
|---|---|---|
| Bare Metal | Supervisor on VPS | supervisorctl start snapcode |
| Containerized | Docker Compose | docker-compose up -d |
| Static | GitHub Pages | git push origin main |