Hosting foundations
Every website uses server resources.
A website or application requires processing power, memory, storage, network connectivity and software services such as a web server, database and email platform.
The main difference between shared hosting, a VPS and a dedicated server is how those resources are allocated, isolated and managed.
Website code, database design, caching, media size, plugins and network latency also affect performance.
Virtual private servers
What is VPS hosting?
A virtual private server is an isolated virtual machine operating on a physical host. The VPS has allocated processing power, memory, storage and an independent operating-system environment.
Unlike ordinary shared hosting, a VPS allows deeper configuration and can support custom applications, background services and specialised software.
Allocated Resources
The VPS receives defined CPU, memory and storage allocations.
Greater Configuration Control
Administrators can configure services, ports, software and operating-system settings.
Easier Scaling
CPU, memory and storage can often be increased without replacing the entire platform.
Management Responsibility
Server updates, security, backups and monitoring must be handled by the customer or a managed provider.
Unmanaged VPS services may leave operating system patching, firewall configuration, malware response and backups entirely to the customer.
Dedicated infrastructure
What is a dedicated server?
A dedicated server is a physical machine assigned to one customer or one organisation. Its processor, memory, storage and network resources are not shared with unrelated hosting accounts.
Dedicated servers provide significant control and can support demanding applications, databases, virtual machines and specialised infrastructure.
High Performance
Physical server resources are available to the customer’s workloads.
Strong Isolation
The environment is not shared with unrelated hosting customers.
Custom Configuration
Hardware, operating systems, storage and network services can be configured for the workload.
Higher Cost
Hardware, management, backup and resilience requirements increase the total cost.
Dedicated servers may be appropriate for
- High-traffic websites and applications.
- Large databases.
- Multiple virtual machines.
- Resource-intensive business platforms.
- Environments requiring specialised configuration.
- Workloads requiring strong physical isolation.
Side-by-side comparison
Shared hosting, VPS and dedicated server compared.
Choosing the platform
Match the environment to the workload.
Review application requirements
Identify required operating systems, databases, programming languages, services and server software.
Estimate traffic and resource demand
Consider normal traffic, peak demand, file storage, database size and background processing.
Define security requirements
Review isolation, firewall, access, monitoring, backup and compliance requirements.
Assess internal technical capacity
Determine whether the organisation can manage the server or requires a fully managed service.
Plan for growth
Consider future users, traffic, databases, integrations and additional applications.
Management models
Managed and unmanaged hosting are not the same.
The hosting type describes the infrastructure. The management model determines who maintains it.
Managed Hosting
The provider handles agreed server updates, monitoring, security, backups and technical administration.
Unmanaged Hosting
The customer receives the infrastructure but remains responsible for operating-system and application management.
Co-Managed Hosting
Responsibilities are divided between the provider and the customer’s internal team.
Application Management
Server management does not always include updates or support for the hosted website or application itself.
Hosting migration
Plan migrations before changing environments.
Moving to a different hosting platform may affect websites, databases, email, DNS, SSL certificates, scheduled tasks and third-party integrations.
Hosting migration checklist
- Inventory websites, databases and email accounts.
- Confirm software and version compatibility.
- Create verified backups before migration.
- Reduce DNS time-to-live values before cutover.
- Test the new environment before switching.
- Confirm SSL certificate installation.
- Validate forms, email delivery and scheduled tasks.
- Retain the old environment until acceptance testing is complete.
Databases, permissions, DNS, email, application settings and background jobs must also be tested.
Final recommendation
Start with the smallest suitable environment.
A business website should not be placed on expensive infrastructure without a clear technical reason. Equally, a critical application should not remain on an undersized hosting package simply to reduce cost.
Choose an environment that meets current needs, supports reasonable growth and can be managed securely.