Deployment module
Understanding Hosting
Compare shared hosting, static hosting, cloud hosting, VPS, dedicated servers, serverless hosting, and managed application hosting in plain English.
Learning Objectives
By the end of this lesson, you'll be able to:
- Compare major hosting models in plain English
- Explain why provider terminology can be inconsistent
- Identify which hosting types are realistic for beginner student projects
- Avoid unnecessary VPS or dedicated server complexity
Why This Matters:
Hosting is where the website lives, but different providers use similar words for very different services.
Before You Start:
You should be familiar with:
- Deployment Is Publishing, Not Just Uploading Review here
Hosting Models in Plain English
Hosting terminology is messy. One provider may call something cloud hosting, another may call a similar product managed hosting, and a third may bundle several services together. Focus on what the host actually does: stores files, runs code, manages servers, provides databases, handles builds or connects domains.
A hosting service is a mix of responsibilities. Some services give you a folder for files and a control panel. Some connect to Git and run your build. Some rent you a server and expect you to configure the operating system. Some hide the server almost completely and run small functions when requests arrive. Beginner deployment becomes easier when you choose the service that matches the site you actually built.
Website files
-> hosting account or platform
-> server resources
-> domain and DNS connection
-> visitor requestsHosting Comparison
| Hosting type | Good for | Technical effort | Typical student use |
|---|---|---|---|
| Shared hosting | Small business and traditional websites | Low to medium | Good |
| Static hosting | HTML, CSS, JavaScript and frontend builds | Low | Excellent |
| Cloud hosting | Applications that need managed infrastructure | Medium to high | Later learning |
| VPS | Custom server applications | High | Usually unnecessary |
| Dedicated server | Large or specialised systems | Very high | Not suitable |
| Serverless platform | Modern apps, APIs and functions | Medium | Later learning |
| Managed application hosting | Framework apps where the platform handles server details | Low to medium | Good after fundamentals |
What Beginners Usually Need
For most beginner work, static hosting and shared hosting are enough. A VPS or dedicated server teaches server administration, not just deployment. That can be valuable later, but it is usually unnecessary for a first portfolio, class exercise or static business website.
Use shared hosting when you need a traditional account with domain tools, email, databases or PHP. Use static hosting when the site is HTML, CSS, JavaScript or a built frontend such as Vite. Use managed application hosting later when the project has server-side framework needs. Treat VPS and dedicated hosting as specialist tools, not a badge of seriousness.
Hosting Knowledge Check
Before moving forward, can you answer these?
- Which hosting types are usually enough for beginner static sites?
- Why is a VPS usually unnecessary for beginner deployment?
- Why should students be cautious with hosting terminology?
Check Your Answers
- Static hosting and, in traditional environments, shared hosting.
- It adds server administration responsibilities that are separate from publishing a static site.
- Providers use terms inconsistently, so students should inspect what the service actually stores, builds, runs and supports.
How confident are you with this concept?
Still confused | Getting there | Got it | Could explain it to a friend
Ready for the Next Deployment Step
Key Takeaways:
- Deployment is a publishing workflow, not just a button.
- The live URL is where deployment evidence is gathered.
- The right hosting path depends on files, update workflow, support needs and ownership.
- Troubleshooting starts with the first meaningful error.
Learning Objectives Review:
Look back at what you set out to learn. Can you now:
- Compare shared hosting, static hosting, cloud hosting, VPS, dedicated servers, serverless hosting, and managed application hosting in plain English. Check!
If you can name which part of the system you are changing, test the live result and record the outcome, deployment is becoming a repeatable workflow.
Think & Reflect:
Deployment evidence
- What would prove this site works for someone else?
Next action
- What should be recorded so this deployment can be repeated later?
Looking Ahead:
Next: continue with Choosing a Hosting Path.
Recommended Next Steps
Continue Learning
Ready to move forward? Continue with the next tutorial in this series:
Choosing a Hosting PathRelated Topics
Explore these related tutorials to expand your knowledge: