What Is a Data Center? Why the World Is Building More—and Why Communities Push Back

You open a banking app, stream a video, save a cloud document, or ask an AI assistant a question.

The screen feels local.

The work often is not.

Somewhere, a physical facility receives electricity and data, runs computers, moves information through networks, removes heat, and keeps backup systems ready if something fails.

That facility is a data center.

A data center is a digital factory: it turns electricity, computing hardware, networks, and cooling into digital services people use every day.

By the end of this article, you will be able to explain what a data center actually does, why more are being built, and how to judge local concerns about electricity, water, noise, jobs, taxes, and infrastructure without reducing the debate to “data centers are good” or “data centers are bad.”

What Is a Data Center?

A data center is a building—or group of buildings—designed to keep computing equipment running continuously.

Inside are servers, storage systems, networking equipment, power-distribution equipment, cooling systems, backup systems, controls, and security.

The IEA describes data centers as facilities housing servers, storage systems, networking equipment, and the auxiliary equipment needed to keep them operating.[1]

The important point is that the servers are only part of the system.

The Contexta Digital Factory Loop

A simple way to understand the facility is as a loop:

Electricity + Data → Compute → Network Output → Heat → Cooling → Continuous Operation

Each part depends on the others.

  • Servers and accelerators perform computation and store information.
  • Fiber and network equipment move data in and out.
  • Transformers and switchgear bring electricity into usable form and protect the system.
  • UPS systems and batteries bridge short interruptions.
  • Backup generators or other backup power support longer failures or emergency operation.
  • Cooling systems remove the heat created by computing.
  • Operations and security teams keep the system available and protected.

This is why a large data center often looks less like an office building and more like a combination of:

computer facility + power system + cooling plant + communications hub.

Are Data Centers Only for AI?

No.

Data centers have existed for decades.

They already support:

  • websites
  • cloud storage
  • video streaming
  • banking
  • online shopping
  • business software
  • maps and games
  • government and enterprise systems

AI adds a new and fast-growing workload, but it does not replace all the older reasons data centers exist.

That distinction matters because “data center growth” and “AI data center growth” are related but not identical.

Why Is the World Building More?

Several trends are arriving at the same time.

  • more cloud software
  • more video and digital media
  • larger backups and storage needs
  • more online financial and public services
  • regional data-residency requirements
  • continued growth in AI training and inference

The most recent IEA outlook projects global data-center electricity consumption rising from about 485 TWh in 2025 to about 950 TWh in 2030. Electricity consumption from AI-focused data centers grows faster and roughly triples over that period.[2]

In the United States, Berkeley Lab’s 2026 update estimates a 2030 reference case of 649 TWh, equal to about 11.8% of total U.S. electricity. Its uncertainty range is 521–843 TWh, or about 9.5%–15.3%.[3]

Those ranges matter.

The buildout is large, but the exact outcome depends on AI adoption, equipment shipments, server utilization, chip efficiency, project delays, and power availability.

The Contexta Growth Driver Stack

It helps to separate the reasons for growth into four layers:

LayerWhat is growing
Everyday digital demandcloud, streaming, storage, transactions, enterprise software
AI demandtraining, inference, reasoning, agents, video and other high-compute workloads
Reliability demandredundancy, multiple regions, backup, disaster resilience
Geographic demandlatency, regulation, data residency, customer proximity

That is why data centers do not simply move to one cold place with abundant water and stay there.

Power, fiber, latency, resilience, regulation, land, workforce, and customer geography all matter.

Why Can a Data Center Be Difficult to Build?

The building itself is only one layer.

1. Electricity must reach the site

A region may produce enough electricity overall and still lack a usable connection at one location.

The site may require transmission upgrades, a substation, transformers, studies, and new protection equipment.

2. The power must be reliable

Digital services are expected to work at night, during bad weather, and during grid problems.

Operators may combine grid electricity, UPS batteries, backup generation, storage, flexible demand, and long-term power arrangements.

3. Computing becomes heat

Almost all electricity entering computing equipment eventually appears as heat.

High-density AI systems make thermal management increasingly important.

Cooling design can depend on climate, chip density, water availability, electricity cost, and local rules.

4. Networks matter too

A facility with plenty of power but weak network connectivity is not a strong digital hub.

Large sites can need multiple independent fiber routes for performance and resilience.

5. Long-lead equipment and permits can control the schedule

Transformers, switchgear, generators, cooling equipment, permitting, utility studies, road work, and specialized labor can all move on a different clock from server procurement.

So Why Do Communities Push Back?

One of the clearest public questions is also one of the simplest:

“If we all use data centers, why are people angry when one is proposed nearby?”

The answer is usually not that residents reject the internet.

The conflict comes from a mismatch of scale:

The digital service can be global. The land, electricity, water, noise, roads, taxes, and infrastructure costs are local.

That creates a distribution question:

Who receives the benefits, and who carries the costs and risks?

The Contexta Global-Service / Local-Footprint Split

Global / distributed benefitLocal / concentrated footprint
cloud and AI servicesland use
storage and online serviceselectricity-system investment
business productivitycooling and water decisions
network resiliencenoise, generators, traffic
regional or national digital capacitylocal tax and infrastructure agreements

This split explains why two people can look at the same project and focus on very different facts.

Public Concern Has Increased in 2026

Pew Research Center’s August 2026 survey found that:

  • 54% of U.S. adults said data centers are mostly bad for the environment
  • 50% said they are mostly bad for home energy costs
  • 49% said they are mostly bad for nearby quality of life

Views on local jobs and local tax revenue were much more mixed: 24% said data centers were mostly bad for local jobs and 22% said mostly good; for local tax revenue, 21% said mostly bad and 22% mostly good.[4]

Those numbers do not tell us whether one specific project is good or bad.

They tell us which questions need better project-level answers.

Concern 1: Will Electricity Bills Rise?

A very large new load may require generation, transmission, substations, and other utility investment.

Whether that raises other customers’ bills depends on the local power system, contracts, rate design, timing, and who pays for the new infrastructure.

Berkeley Lab’s 2026 large-load tariff review focuses on exactly this problem: utilities and regulators are creating rate structures and service agreements to manage risks such as insufficient supply, underused investment, and cost shifting to other customers.[5]

So the useful local question is not:

“Do data centers always raise electricity prices?”

It is:

“What infrastructure does this project require, and how are its costs and risks allocated?”

Concern 2: How Much Water Will It Use?

There is no single water-use answer for all data centers.

Cooling systems differ.

Climate differs.

Some facilities use evaporative cooling.

Others use closed-loop systems or designs that reduce direct onsite water use while potentially changing electricity use.

GAO has emphasized that generative AI uses significant energy and water resources, but detailed company reporting remains limited and water-use estimates are uncertain.[6]

That means a community should ask for project-specific answers:

  • what cooling architecture?
  • what water source?
  • annual and peak-day use?
  • potable or recycled water?
  • what changes during hot weather?

Concern 3: What About Noise?

Noise can come from cooling equipment, transformers, generators, turbines, pumps, and construction.

The relevant questions are not only average decibels.

Distance, frequency, nighttime operation, testing schedules, barriers, and background sound all affect what neighbors experience.

A project-specific noise study is more useful than a generic claim that “data centers are quiet” or “data centers are loud.”

Concern 4: What About Air Emissions?

Backup diesel engines and onsite gas generation can produce air emissions when they operate.

EPA maintains Clean Air Act resources specifically for data centers and stationary engines.[7]

The local impact depends on:

  • number and size of units
  • fuel
  • testing frequency
  • actual operating hours
  • emission controls
  • distance from nearby homes

Again, the answer is project-specific.

Concern 5: How Many Jobs Are Permanent?

Data centers can bring large construction projects, supplier work, electrical and mechanical trades, maintenance work, tax revenue, and local service demand.

But construction employment and permanent operating employment are different categories.

A useful announcement should separate:

  • construction jobs
  • permanent onsite jobs
  • contractor and supplier jobs
  • tax revenue before and after incentives
  • public infrastructure commitments

This prevents a billion-dollar investment figure from becoming a substitute for a local-benefit calculation.

The Contexta Benefit–Burden Ledger

Instead of asking whether a project is simply “good” or “bad,” put both sides on the same page.

Possible local benefitQuestion that verifies it
construction workHow many jobs, for how many years, and how much local hiring?
permanent employmentHow many full-time operating jobs remain after construction?
tax revenueWhat remains after exemptions and incentives?
new grid/fiber infrastructureWho owns it, who pays for it, and who else can use it?

Then do the same for potential burdens:

  • grid investment
  • water demand
  • noise
  • air emissions
  • traffic
  • land-use change
  • risk if the project is delayed or canceled

The Contexta Community Due-Diligence Test

If a data center is proposed near you, seven questions reveal more than most headlines.

  1. Power: What MW is required in phase one and at full buildout?
  2. Grid cost: Who pays for generation, transmission, substations, and transformers?
  3. Downside risk: What happens to those investments if the project shrinks, slips, or is canceled?
  4. Cooling and water: What system is used, from which source, and at what peak demand?
  5. Noise and emissions: What equipment runs routinely, during testing, and during emergencies?
  6. Jobs: How many are construction jobs versus permanent operating jobs?
  7. Taxes and benefits: What net local revenue remains after incentives, and what public services must expand?

These questions turn a culture-war-style argument into infrastructure due diligence.

What About the Benefits?

Data centers can create real benefits.

Depending on the project, these may include:

  • construction spending
  • supplier contracts
  • electrical, mechanical, network, and operations jobs
  • property-tax or negotiated public revenue
  • new substations and fiber
  • clean-energy or storage projects
  • long-term demand for local technical services

But none of those benefits should be assumed from the project’s headline investment value alone.

They should be checked against contracts, hiring plans, utility agreements, tax incentives, and actual project design.

Why the Debate Is Hard

One reason data-center debates become heated is that different sides often answer different questions.

A technology company may ask:

How quickly can we add compute?

A utility may ask:

How do we serve the load without creating reliability or financial risk?

A local government may ask:

What investment and tax base will remain here?

A nearby resident may ask:

What happens to my bill, water, roads, noise, and landscape?

All four questions can be legitimate at the same time.

The Contexta Four-Lens Test

For any proposed data center, read it through four lenses:

Digital Need → Physical System → Local Footprint → Cost/Benefit Allocation

Digital Need: What service or workload requires the capacity?

Physical System: What power, cooling, network, and backup systems are needed?

Local Footprint: What land, water, noise, traffic, and emissions appear locally?

Cost/Benefit Allocation: Who pays, who gains, and who carries risk if plans change?

What Should You Watch Next?

  • Electricity demand: do 2030 forecasts move up or down as inference efficiency and AI use change?
  • Rate design: do utilities increasingly require large loads to protect other customers from stranded costs?
  • Water disclosure: do companies publish more site-level cooling and water data?
  • Cooling architecture: how quickly do liquid and closed-loop systems change local water needs?
  • Local agreements: are jobs, tax revenue, road upgrades, and community benefits contractually defined?
  • Public acceptance: does concern keep rising as more projects move into new communities?

The Main Idea

A data center is not simply a warehouse full of computers.

It is a physical system that turns electricity and information into digital services.

That is why the world is building more of them.

And it is also why local communities ask difficult questions.

The useful question is not “Are data centers good or bad?” It is “What does this specific project need, what does it deliver, and how are its benefits, costs, and risks shared?”

Continue Reading

Key Terms

  • data center: a facility that houses computing, storage, networking, power, cooling, backup, and support systems
  • server: a computer that processes, stores, or serves data and applications
  • accelerator: specialized computing hardware such as a GPU used for high-performance workloads including AI
  • UPS: uninterruptible power supply that bridges short power interruptions
  • cooling system: equipment that removes heat from IT equipment and the facility
  • data residency: requirements or choices governing where certain data are stored or processed
  • large load: a customer whose electricity demand is large enough to affect grid planning or utility investment
  • cost allocation: deciding which parties pay for infrastructure and financial risk
  • full buildout: the final planned scale of a multi-phase project
  • community benefit: a local economic or infrastructure gain that should be verified through actual agreements and outcomes

Sources

  1. IEA — Energy and AI: Energy demand from AI — data-center components and energy-system context.
  2. IEA — Key Questions on Energy and AI, 2026 — global electricity-demand outlook and social-acceptance context.
  3. Lawrence Berkeley National Laboratory — United States Data Center Energy Usage Report: 2025 Update — U.S. 2030 electricity scenarios.
  4. Pew Research Center — Americans’ views of data centers have turned more negative, September 2026.
  5. Lawrence Berkeley National Laboratory — Electricity Rate Designs for Large Loads: 2026 Update.
  6. U.S. GAO — Generative AI’s Environmental and Human Effects — energy, water, and reporting uncertainty.
  7. U.S. EPA — Clean Air Act Resources for Data Centers — stationary-engine and air-permitting context.

Status checked September 30, 2026. The Digital Factory Loop, Growth Driver Stack, Global-Service / Local-Footprint Split, Benefit–Burden Ledger, Community Due-Diligence Test, and Four-Lens Test are The Contexta analytical frameworks. Resource use, jobs, tax effects, noise, water demand, and electricity-price effects vary materially by project, technology, utility system, and local agreement.