From understanding reliability and availability, this talks walks you through the why and the how of building multi-region, active-active applications, and especially why serverless is a great fit.
Reliability can be defined as the probability that a system will produce correct outputs up to some given time t.[5] Reliability is enhanced by features that help to avoid, detect and repair hardware faults. A reliable system does not silently continue and deliver results that include uncorrected corrupted data. Instead, it detects and, if possible, corrects the corruption, for example: by retrying an operation for transient (soft) or intermittent errors, or else, for uncorrectable errors, isolating the fault and reporting it to higher-level recovery mechanisms (which may failover to redundant replacement hardware, etc.), or else by halting the affected program or the entire system and reporting the corruption. Reliability can be characterized in terms of mean time between failures (MTBF), with reliability = exp(-t/MTBF).[5]
Note the distinction between reliability and availability: reliability measures the ability of a system to function correctly, including avoiding data corruption, whereas availability measures how often the system is available for use, even though it may not be functioning correctly. For example, a server may run forever and so have ideal availability, but may be unreliable, with frequent data corruption.
Does a region Fail?
Full region: no
Individual services can fail region-wide
Most of the time, configuration issue
Leading to cascading failures.
Eventual consistency
Works similar to existing Intra Region VPC Peering
2. Data always stays on the AWS backbone
3. Data always encrypted by default
4. No need to use Gateways, third-party VPN solutions to connect across regions.
5. No additional charges for using interregion VPC peering. Customers pay standard data transfer rates
Route end-users to the AWS region that provides the lowest possible latency.
Route end-users to a particular endpoint that you specify based on the end user’s geographic location.
Specify the frequency (“weights”) with which different DNS responses are returned to end users
Route your website visitors to an alternate location to avoid site outages
The truth is, the future is always in the making. It’s engineers and wild thinkers that are helping to create the world of tomorrow.
It’s customers like tusimple, revolutionizing the commerical trucking industry, arterys saving lives through 4d medical imaging, duolingo teaching language around the world.. It’s customers like you that are helping to build this.
Together, we can tackle some of the worlds most challenging problems, and together we can continue to build a smater future.