What is a workload?
It’s such a simple question that surely it doesn’t need answering, does it?
But this is the age cloud, so perhaps it does.
We are using cloud technologies to “separate out and compartmentalise” tasks in new hosted, virtualised cloud environments — often between private and public clouds to create the notion that we call hybrid.
The need to know what workload goes where, in the service-based world of cloud computing is more pressing now.
At the most obvious and simplistic level we can say that the term workload simply describes an amount of work attributed to a defined computing block at any moment (or, more accurately, period) in time.
But onward from here we may also consider that workloads can be considered self-contained entities, often with no inter-related programmatic dependencies.
In simpler terms this means that a workload is a computing task that exists with a discrete, isolated and detached set of application logic (with specific policies, rules and behavioural characteristics) that can be executed independently (and autonomously if needed) of a specific parent (or related) application so that a specific computing function can be carried out.
From here we can start to talk about Intelligent Workload Management (IWM) and how software application development can take advantage of a higher level of workload-aware intelligence.
Workload means something more in 2015, get used to it.