Which workloads are suitable for virtual IT solutions?

Workloads are suitable for virtual IT solutions when they can run reliably in a shared, centrally managed environment without requiring dedicated physical hardware. The strongest candidates are workloads with predictable resource needs, established network access requirements and clear controls for identity, data protection, backup and recovery.

Business applications are often well suited to virtual delivery. Customer relationship management, accounting, enterprise resource planning, document management, project management and other line-of-business applications can be hosted on virtual servers or delivered through virtual desktops, provided the application supports the required operating system and hosting model. Centralising these applications can also simplify access management, patching and the allocation of computing resources.

Suitability depends on more than whether an application can technically be virtualised. The assessment should consider:

• Whether the software vendor supports virtual or hosted deployments
• How many users connect concurrently and how their usage varies
• The application’s processor, memory, storage and graphics requirements
• Whether it relies on local devices, specialist drivers or physical peripherals
• How it connects to other applications, databases and business processes
• What data protection, audit and retention controls are required

File services and business data are another common workload category. Shared documents, operational records, templates and structured databases can be held in a centrally managed environment when permissions, version control, backup and recovery have been properly designed. This is particularly relevant where staff work from more than one site or need consistent access to the same information.

Data-intensive workloads require closer examination. Large databases, media libraries, engineering files and transactional systems may be suitable, but their storage performance, input/output patterns and backup windows must be understood first. A virtual platform that has adequate capacity for ordinary office documents may not be appropriate for a workload that constantly processes large files or performs frequent database transactions.

Virtual desktops and remote application access can suit organisations whose users need a consistent working environment across offices, home locations or managed devices. They are useful where applications and data need to remain centrally controlled, or where users require access to the same desktop configuration. The design must account for screen responsiveness, printing, audio, video, local file transfer and the quality of the connection between the user and the hosted environment.

Collaboration and communication workloads can also be virtualised or centrally delivered. Examples include internal portals, intranets, workflow tools, scheduling systems and applications that support shared working. These workloads are generally easier to accommodate when they use standard web protocols and do not depend on specialist local hardware. Their suitability still depends on identity integration, permissions, data location and how access is secured.

Development, testing and temporary environments are often good candidates because virtual infrastructure allows separate environments to be created, copied, isolated and removed without purchasing dedicated hardware for each one. Development teams can use this approach to test application changes, operating-system updates or integration work. Controls are needed to prevent test data containing sensitive information from being exposed or copied without authorisation.

Some workloads are possible in a virtual environment but need additional design controls. These include:

• Databases with high transaction rates or strict storage latency requirements
• Applications that need substantial memory or processor capacity
• Systems that exchange data continuously with equipment or other sites
• Workloads requiring graphics processing or specialist display performance
• Applications with complex licensing rules tied to physical hardware
• Systems that must remain available during maintenance or infrastructure changes

Workloads are usually less suitable when they depend on dedicated hardware, direct access to a physical device, highly specialised processing or exceptionally consistent low latency. Examples may include some industrial control systems, specialist imaging applications, hardware-bound licensing models and equipment-management software. This does not automatically rule out virtualisation, but it may mean that only part of the workload is virtualised while the hardware-dependent component remains physical.

Dependencies should be mapped before making a decision. A seemingly simple application may rely on a local database, file share, printer, domain service, scanning device, authentication system or connection to a manufacturing or logistics platform. Moving the application without its dependencies can create performance, security or operational problems. Reviewing the complete service rather than just the application server gives a more accurate view of suitability.

A practical assessment normally records each workload’s owner, users, data sensitivity, dependencies, resource consumption, recovery requirements and acceptable service interruption. It should then compare those requirements with the proposed virtual platform, connectivity, security controls and support arrangements. S2 Technology Group can use this type of assessment when advising small and medium-sized organisations on infrastructure design, helping distinguish workloads that are suitable for virtual delivery from those that need dedicated or hybrid arrangements.