
Why Businesses Have Multiple Branches: Understanding AWS Regions & Availability Zones
Learn AWS Regions and Availability Zones through a simple business analogy. Discover how AWS improves performance, resilience, and availability.
Series: Cloud for Non-Cloud Engineers (2 articles)
- 2Why Businesses Have Multiple Branches: Understanding AWS Regions & Availability Zones This article
If you've ever opened the AWS Console for the first time, one of the first things you probably noticed was the Region selector in the top-right corner. You might have seen options like US East (N. Virginia), Europe (London), Africa (Cape Town), or Asia Pacific (Singapore) and wondered why AWS needed so many different locations.
After selecting a Region, you may have come across another unfamiliar term: Availability Zone.
At first glance, these concepts can feel like unnecessary cloud jargon. Why can't AWS simply have one massive data center where everything runs? Wouldn't that be easier to build and manage?
The answer becomes surprisingly simple once we step away from cloud computing for a moment. Before we talk about AWS, let's imagine you're building a business.
Imagine You Own a Successful Supermarket
Suppose you've just opened a supermarket in Lagos.
Business is going well. Customers are happy, sales are increasing, and before long your store has become one of the busiest supermarkets in the city.
As your reputation grows, people begin travelling from neighbouring cities to shop at your store. Some customers drove from Ibadan. Others travel from Abeokuta. A few even come from Benin City because they've heard great things about your prices and customer service.
At first, this sounds like a good problem to have but after a while, you begin to notice several issues.
Since customers are travelling long distances just to buy groceries, the supermarket becomes overcrowded during peak hours. Deliveries take longer because every supplier must deliver to a single location. Most importantly, if anything happens to that one supermarket, perhaps a fire, a prolonged power outage, or structural maintenance, your entire business comes to a halt.
Naturally, you begin to ask yourself a simple question:
"Why am I trying to serve everyone from one building?"
The obvious solution isn't to make the supermarket even bigger. Instead, you open more branches.
Perhaps one in Abuja, another in Port Harcourt and another in Ibadan. Now, instead of asking customers to travel hundreds of kilometres, they simply visit the branch closest to them.
Your customers receive faster service, your stores become less crowded, and if one branch experiences a problem, the others continue operating and without realizing it, you've just applied one of the same principles AWS uses to design its cloud infrastructure.
Successful Businesses Rarely Operate from One Location

If you look around, you'll notice that almost every large organization follows this same philosophy.
Banks don't operate from a single office that serves an entire country. Instead, they establish branches in different cities so customers can access financial services without travelling unreasonable distances.
Hospitals are distributed across regions because patients need healthcare close to where they live. Universities establish multiple campuses to serve students from different parts of the country. Logistics companies operate several warehouses so that deliveries can be completed quickly and efficiently.
The reason behind all of this isn't simply about convenience because distributing operations across multiple locations improves performance, reduces congestion, and protects the organization against failures in any one location.
AWS approaches cloud computing in exactly the same way.
For example, AWS has Regions in:
- North America
- South America
- Europe
- Africa
- Asia Pacific
- Middle East
When you launch an AWS resource, such as an EC2 instance or an Amazon S3 bucket, one of the first decisions you'll make is which Region should host that resource.
That decision is more important than many beginners realize.
Regions Also Help Meet Legal and Business Requirements
Imagine your supermarket sells prescription medicine.
The government may require customer records to remain within the country where they were collected. Even if you own stores in several countries, you cannot freely move sensitive customer information wherever you like.
Businesses encounter similar requirements every day.
Some organizations must store data within specific countries because of local regulations. An example is the Central Bank of Nigeria (CBN) ordering all banks, fintechs, and payment service providers to move and store all payment transaction data generated in Nigeria onto local servers by January 1, 2027. Others choose a particular Region because certain AWS services are available there first, while pricing can also differ slightly between Regions.
For these reasons, choosing a Region is often a business decision as much as it is a technical one.
If Regions Are Cities, What Are Availability Zones?

Let's zoom back into Lagos. Instead of operating one supermarket in the entire city, imagine you decide to build three separate branches.
One is located in Ikeja, another is in Lekki and the third is in Yaba.
Although they all belong to the same company, each branch has its own staff, inventory, power supply, storage facilities, and security systems.
Now imagine that heavy flooding forces the Lekki branch to close for several days. Customers can still shop in Ikeja or Yaba. The company continues operating because the business was never dependent on a single building.
This is exactly how Availability Zones work.
Within every AWS Region are multiple Availability Zones. Each Availability Zone consists of one or more physically separate data centers designed to operate independently from the others.
Even though they belong to the same Region, they have separate infrastructure, including power, cooling, and networking.
At the same time, AWS connects these Availability Zones using high-speed, low-latency networks so they can work together seamlessly.
A Practical AWS Example

Imagine you're building an online store for customers across Nigeria and neighbouring countries.
- You decide to deploy your application in an AWS Region that is geographically close to your users.
- Instead of launching your web application in only one Availability Zone, you deploy it across two.
- Your database is also configured to replicate data between those Availability Zones.
- One afternoon, an unexpected infrastructure issue affects one Availability Zone.
Because your application was designed to run across multiple Availability Zones, traffic is automatically directed to the healthy environment. Most customers continue shopping without even realizing that part of the infrastructure experienced a problem.
That resilience is the result of designing your application around AWS's global infrastructure.
Best Practices
As you begin working with AWS, there are a few principles worth remembering.
- Choose a Region that is geographically close to your primary users whenever possible, as this generally provides better performance. Consider compliance requirements before selecting a Region, particularly if your application stores sensitive information that must remain within a particular country or jurisdiction.
- For production workloads, avoid relying on a single Availability Zone. Distributing applications across multiple Availability Zones improves resilience and reduces the impact of infrastructure failures.
- Finally, remember that using additional Regions introduces additional complexity and cost. Many applications perform perfectly well within a single Region spread across multiple Availability Zones.
When people first encounter AWS Regions and Availability Zones, they often assume these are unique cloud concepts that require a completely different way of thinking but in reality, they reflect a strategy that successful organizations have been using for decades.
In the next article, we'll explore another AWS service that many people misunderstand at first: Amazon S3, and why it's much closer to a warehouse than a hard drive.
Series: Cloud for Non-Cloud Engineers (2 articles)
- 2Why Businesses Have Multiple Branches: Understanding AWS Regions & Availability Zones This article
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article