AWS Global Accelerator explained, versus CloudFront, Route53.

AWS Global Accelerator compared to CloudFront, Route53. Why we need Global Accelerator? Use cases for multiple data centres, globally distributed users. Features set. MXX reccomendation.

[pcs]

Perfect one. Future videos with such visual are highly appreciated

[artemyevtushenko]

Amazing job! This was exactly what I was looking for.

[cesar_zapata]

This explanation is brilliant. Couldn't be clearer. Thank you. And thanks for using very visual slides, that helps a lot.

[mashadol]

Precisely what I needed - concise and to the point. Thank you!

[najimahmed]

Subscribed, super awesome explanation, crystal clear!

[rajeevradnair]

Short, precise, and very informative!!

[Ijusthaveacamera]

Thank you for this short and detailed explanation! It solved a lot of doubts.

[lithikadhulipalla]

Thanks for the overview of the differences and use case of Global Accelerator and CloudFront. Simple and clear content.

[vidyakrishnan]

Excellent video, thank you so much for sharing !

[surendrababu]

Beautifully explained. thank you very much

[edgewalllimited]

Great explanation. Clear and precise. Thanks

[СвадебноеВЕДОМСТВО-тр]

First good explanation of global accelerator!

[gustavovargas]

Great!!!, Im from Chile and we have a Edge location in Santiago, Chile, that's nice for Cloudfront and Global Accelerator. Thanks you for your great video.

[andreiduca]

You can have multi-region failover with CloudFront as it's support multiple origins. The only limitation that you have is that only GET and HEAD methods are supported. But it's really cool that if an origin fails CloudFront behind the scenes sends the request to the next origin the only impact being a higher response time.

[TheDoktorot]

Great video! Can you please point me to an article or explain in short how to use CloudFront and Global accelerator combined? thanks!

[oleksandrgolovatyi]

Very good ! thank you. Interesting to check if it's possible to unite distributions for ALB's in a different regions in one group and achieve region failover in this case ? I guess this is the whole purpose of having grouping function, so Cloudfront could also give a multi-region failover

[lb]

Beautiful explanation. Could you also show how those 2 IPs and multi region, say ALBs in 4 regions really work together in Global Accelerator?

[HaimNachmias]

Beautiful explanation, thank you! Very clear.
Just one question: In this video, you ended up recommending using both CloudFront and Global Accelerator for multi-region websites (5:47), while in the article's conclusions you have recommended on CloudFront + Route53 (Schema 2: Multi regional setup with CloudFront). Why is that?
It seems that CloudFront+Accelerator is preferable in terms of performance and availability, but it's a little bit more complex and expensive.

[ericacm]

When comparing the pricing of Route53 and Global Accelerator, one other thing to mention is besides the hourly rate (which you mentioned), GA has a data transfer cost. Route53 does not have a data transfer cost. If you serve a lot of traffic GA could become pricey. Route53 has per zone and per query costs (except for Alias records). But these are not proportional to the data transfer costs.

[arkadiyshuvaev]

Great video, thank you! BTW, are there real figures of latency between AWS backbone access points? Just out of curiosity, where did you get the mentioned 120 ms latency (1:43)? And again, thank you for your video!