Module 67: Hosting Technologies
Choosing by need and cost
🏠The everyday picture
Choosing transport: a bicycle, a scooter, a car, or hiring a taxi. Each is right for some trips. The best choice depends on the distance, the load, the budget, and whether you want to do your own repairs.
📘What it really is
A practical way to choose:
- Start from needs (Lesson 1), not from a favourite provider.
- Split the app into parts; each can be hosted differently:
- static frontend → shared hosting or a frontend platform;
- API → VPS, PaaS or containers;
- database → managed database (recommended) or self-run on a VPS;
- files → object storage (Module 45).
- Count total cost, not just the price tag:
- the monthly bill, now and at ten times the traffic;
- your time maintaining servers;
- the cost of downtime or data loss;
- bandwidth and storage charges, which can surprise.
- Prefer simplicity for small teams: fewer moving parts, managed services for hard things (databases, backups).
- Write down the decision and the conditions that would change it ("move to a bigger VPS above 1,000 daily users").
A sensible starting set-up for your CRM:
- frontend on Hostinger or a frontend platform;
- API in a container on a small VPS (Course 6.1 skills) or a PaaS;
- managed PostgreSQL in an Indian region, with automatic backups;
- object storage for uploads.
🖱️Try it
Using hosting-needs.md, compare three complete set-ups for your CRM (for example: all on one VPS; VPS plus managed
database; PaaS plus managed database). Estimate monthly cost and your weekly maintenance time for each, choose one, and write
the decision and its review conditions.
✅Quick check
Why might a VPS that's cheaper per month cost more overall than a managed platform?
Show the answer
Your time spent maintaining it, and the risk of downtime or data loss, add to the real cost.
Should the frontend, API and database all be hosted the same way?
Show the answer
Not necessarily; each part can use the hosting that suits it.