Computer Weekly features: August 2022

I am working on the features below for Computer Weekly (for late August/early September publication). Deadlines for contributions noted against each article.

Data classification policy

How do you write a data classification policy, and more importantly, what should it cover?

In this feature we will look at:

  • What do we understand by data classification?
  • What is it used for? (eg for, backups, compliance, storage management and budgeting)
  • What does such a policy take into account?
  • What are the benefits of data classification?
  • What are the key elements of a data classification policy, and how would you start drafting one?

Deadline for contributions: Friday 5th August

How do we measure cloud storage TCO?

What are the key things to take into account when working out cloud storage costs as a total cost of ownership?

This piece will drill down into the main cost areas for cloud storage services. These could include capacity, storage tiers, AZs and egress costs, though that is not an exhaustive list. The piece will also compare these costs with the costs of on-premises storage technology.

In addition, we will look at which workloads are the most (cost) effective in the cloud, both for long term and “boost” usage and which, for now, are not.

Deadline for contributions: Friday 12th August.

Cloud bursting 

This piece is an “explainer setting out when, why and how firms will “burst” their workloads to the cloud. The piece will cover:

  • What is cloud bursting?
  • What are the benefits of cloud bursting?
  • What type of workloads can benefit from cloud bursting?
  • What are the limits / obstacles to cloud bursting?
  • What workloads are never (or almost never) likely to use cloud bursting?
  • How difficult is cloud bursting?

Deadline for contributions: Friday 19th August.

For all these articles please contact me by email in the first instance, if you are contributing to a specific article please note that in the subject line. If you are responding on behalf of more than one client, please use separate emails. Many thanks.