Introduction:
Table of Contents
In 2006 AWS began offering IT infrastructure services to businesses as web services commonly known as cloud computing. One of the benefits of cloud computing is to reduce infrastructure expenses with your business.
Why cloud infrastructure matter?
The AWS global cloud infrastructure is the most secure, extensive, and reliable cloud platform, offering over 175 fully-featured services from data centers globally. Whether you need to deploy your application in a single click, or you want to build and deploy specific applications closer to your end-users with millisecond latency, AWS provides you the cloud infrastructure where and when you need it.
Magic Quadrant for cloud infrastructure as a service:
AWS global infrastructure:
*AWS is a cloud computing platform that is globally available.
*AWS is available in 24 regions and 77 availability zones.
*The following are the components that make up the AWS infrastructure are
1.Availability zones
2.Region
3.Edge locations
4.Region edge caches.
Availability zone:
An AZ is one or more discrete data centers with redundant power, networking, and connectivity in an AWS region. The availability zone allows you to operate production applications and databases that are more highly available. An AZ consists of multiple servers.
List of Aws regions and availability zones:
Region:
A region is a geographical area where we cluster all data centers. We call each group of the logical data center as an availability zone.
EDGE LOCATIONS:
*Edge locations are the endpoints for AWS used for caching content.
*Edge locations consist of CloudFront, Amazon content delivery network(CDN).
*Currently there are 150 edge locations.
*, for example, some user accesses your website from Singapore then this request would be redirected to the nearest edge location where cached data can be read.
REGIONAL EDGE CACHE:
*AWS announced a new type of edge location in November 2016 known as a regional edge cache.
*A regional edge cache lies between cloud front origin servers and the edge location.
*A regional edge cache has a large cache than an individual edge location.
*When the data is removed from the edge cache the data redirected to regional edge cache.
*When the user requests the data then the data is no longer at the edge location. therefore, the edge location retrieves the cached data from the regional edge cache instead of origin servers that have high latency.
