Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

> Africa (Cape Town) is the 23rd AWS Region, and the first one in Africa. It is comprised of three Availability Zones

That means 3 data centres.



view as:

A common misconception, but no, AWS AZs are not DCs. A single AZ may be composed of multiple data centers[1], and a region may incorporate facilities that do not serve a public AZ[2], or that supply other capabilities[3].

[1] They'd be necessarily close together due to speed-of-light constraints.

[2] You may infer this from S3's triple-zone replication, which is still somehow magically fulfilled in regions that only have two public AZs.

[3] most obviously, Direct Connect.


To clarify, it means at least 3 DCs per AWS documentation.

https://aws.amazon.com/about-aws/global-infrastructure/regio...


Oh, very nice link, thanks!

> AZ’s are physically separated by a meaningful distance, many kilometers, from any other AZ, although all are within 100 km (60 miles) of each other.

This answers my previous question I guess

EDIT: well, actually, no. I wanted to know distance between DC in the same AZ :)


If you really want to know, you can look it up on wikileaks

https://wikileaks.org/amazon-atlas/map/


Do you happen to know how physically far can be AZs in the same region? The EBS sticking to the same AZ hints that they may be not that close, but I'm also very surprised to discover that 1 AZ != 1 DC

Most AZs are 1 DC, but some are too large to fit in a single building.

I don't think there is a distance limit between AZs but instead a latency limit. James Hamilton covered it in one of his keynotes a few years ago.

EBS sticking in the same AZ has nothing to do with distance and everything to do with keeping failures within an AZ


> I don't think there is a distance limit between AZs but instead a latency limit

Ok, fleshing that out via google:

"The connection between AZs is expected to typically achieve low single-digit millisecond latency between them on average."

https://knowledgebase.progress.com/articles/Article/expected...

and

1 light-millisecond = 299792.458 meters, so nearly 300 km / 186 miles.

https://www.translatorscafe.com/unit-converter/en-US/length/...

So in 2 milliseconds, light travels 599km or 372 miles.

That's a _hard_ limit. IIRC, modern communications is at a fraction of lightspeed, which would lower it.

There's no reason _not_ to have the AZs for a region in the same metro area, so separated by 10s of km, tops.

10km = 0.0333 light-milliseconds.


You need to take into account the speed of light in fiber optics and switching latency. For fiber you're looking at about 5 µs/km

> about 5 µs/km

Which puts it at 200km in a millisecond (5 microseconds is 1 / 200 of a millisecond.) Like I said "modern communications is at a fraction of lightspeed", although I didn't want to guess what fraction. But 200 / 600 = 1/3 is a reasonable fraction, seems legit.


> EBS sticking in the same AZ has nothing to do with distance and everything to do with keeping failures within an AZ

But they could be synced and if one AZ goes down another is elected as the primary copy. Most storage solutions handle that.


You're right, I should have said "at least three data centers"

It was in response to parent comment saying "the datacenter", which seems to be assuming that there was only one. But there will be multiple.


Quite. South Africa has a string of rolling black-outs though...some lasting as long as 8 hours at a time during bad spells. Some you'll be running off generators as primary source (with no backup) far more than you'd normally expect even if you have multiple data centres.

Easiest way around that is to locate it in an area exempt from the rolling blackouts as I said.


There hasn't been an 8 hour blackout in Cape Town due to loadshedding. The longest was 4 hrs I believe. They have a plan to get this sorted out in a year and a half, in the meantime DC's will just have to rely on their power redundancy (which has to be in place anyway).

Legal | privacy