Software Engineering Roadmap

Learn how to build, test, deploy, and maintain robust software systems.

Overall Progress0%

Deployment & Hosting

Explanation

Deployment is the process of taking your software from a development environment and putting it somewhere real users can reach it. Hosting provides the compute, networking, and storage that make that possible, and a good deployment also sets up DNS, HTTPS, configuration, logging, monitoring, and a recovery plan. This lesson covers the cloud service models (IaaS, PaaS, SaaS), how DNS and HTTPS turn a name into a secure, reachable service, and what a production checklist looks like. The examples mention Vercel and Render as platforms, but the concepts apply to any hosting provider.

What Is Deployment?

Development environment

↓

Deployment

↓

Production environment

When software goes to production, it becomes publicly reachable, so configuration, security, and reliability start to matter in new ways.

What Does Hosting Provide?

Compute (where your code runs).
Networking (how users reach it).
Storage (databases and files).
Runtime and availability.

Cloud Service Models

Model	You manage	Provider manages	Example
IaaS	VMs, OS, runtime, app	Physical hardware	AWS EC2
PaaS	Your app and data	Runtime, scaling, OS	Heroku, Render
SaaS	Your account and data	Everything	Gmail, Slack

IaaS vs PaaS

IaaS gives you raw virtual machines and full control, at the cost of managing everything.
PaaS manages the runtime and scaling for you, so you focus on the application.

A Production Architecture

User

↓

DNS

↓

HTTPS / CDN

↓

Application

↓

Database

↓

External services

DNS

Domain name

↓

DNS lookup

↓

IP address / target

Record	Meaning
A	Maps a name to an IPv4 address
AAAA	Maps a name to an IPv6 address
CNAME	Alias one name to another

HTTPS and TLS

HTTPS encrypts traffic between the browser and the server using TLS. A certificate proves the server’s identity and enables that encryption, which is why production sites should always use HTTPS.

Environment Configuration

Production needs its own configuration and secrets, separate from development. Pass them through environment variables or a secret manager, never hardcoded.

Database Deployment

Run schema changes with migrations, not manual edits.
Have a backup and a restore strategy.
The database is often deployed separately from the application.

Logging and Monitoring

Logs tell you what happened.
Metrics show trends (requests, errors, latency).
Health checks tell you whether the service is up.
Alerts notify you when something is wrong.

Availability and Scaling

	Vertical scaling	Horizontal scaling
How	Bigger machine	More machines
Limit	Hits a hardware ceiling	Needs load balancing and stateless design
Use	Simple early growth	Large or elastic workloads

Deployment Strategies

As covered in CI/CD, rolling, blue/green, and canary deployments let you release with lower risk and a clear rollback path.

A Production Checklist

Environment variables and secrets set correctly.
HTTPS and DNS configured.
Database migrations applied, with backups.
Logs and monitoring in place.
Health checks responding.
Error handling and resource limits set.
A rollback plan exists.

Examples

A full-stack deployment

Frontend and backend hosted separately, talking over HTTPS.

text

1Frontend (Vercel) → HTTPS → Backend API (Render) → Database

Output

(one production system across two hosts)

Key Takeaways

Deployment moves software to a production environment.
Cloud models are IaaS, PaaS, and SaaS, with different responsibility splits.
DNS maps names to addresses; HTTPS encrypts and verifies.
Manage secrets and configuration through the environment.
Apply database migrations and keep backups.
Logging, monitoring, health checks, and a rollback plan are essential in production.

← PreviousContainerization