(A data centre in Hamina, Finland. Source: Google)
Not long ago, European customers of the global public cloud vendors relied upon a single data centre ‘region’ for all their cloud computing needs. From Lisbon to Lviv, Kiruna to Kalamata, customers of Amazon Web Services (AWS) and Microsoft Azure sent everything to Ireland, and customers of the Google Cloud Platform (GCP) sent everything to Belgium. And, mostly, public cloud’s early adopters in Europe just got on with it.
For the majority of public cloud workloads, storing and processing data somewhere in the European Economic Area (EEA) really was — and is — good enough. Network latency was mostly low enough not to be a problem, and European regulations covered the main use cases well enough to appease all but the most cautious lawyers.
But connections can always be faster, and there are still use cases in regulated industries and government where keeping personal data inside specific geographic borders is either essential or encouraged. And, more and more often these days, customers just seem to feel happier when their data doesn’t leave the country. Mostly, no law requires it, and no regulation recommends it. But it’s still happening. We should all be pushing back against this odd trend towards data balkanisation, much harder than we are.
Two weeks on, the result of the UK referendum on membership of the European Union (EU) continues to reverberate around the world. Forrester provided advice for clients needing to understand the business implications. Looking at the specific impact on public cloud deployments in Europe introduces a number of additional points. These are best considered in three separate contexts:
that of companies wishing to serve customers in the UK
that of companies wishing to serve customers in the remaining 27 EU member states (the EU27)
that of companies wishing to serve customers in the EU27 from a base in the UK.