AWS re:Invent 2022 - Multi-Region design patterns and best practices (ARC306)

Поделиться
HTML-код
  • Опубликовано: 10 июл 2024
  • In this session, dive deep on the topic of multi-Region design and explore different ways to implement such architectures. Consider how to think about multi-Region architectures and what is included from a cost, operations, and engineering perspective. Also learn about AWS service features that can help you build multi-Region solutions, including Amazon Route 53 Application Recovery Controller, Amazon CloudFront Functions, Amazon Aurora Global Database, Amazon DynamoDB global tables, and more.
    Learn more about AWS re:Invent at go.aws/3ikK4dD.
    Subscribe:
    More AWS videos bit.ly/2O3zS75
    More AWS events videos bit.ly/316g9t4
    ABOUT AWS
    Amazon Web Services (AWS) hosts events, both online and in-person, bringing the cloud computing community together to connect, collaborate, and learn from AWS experts.
    AWS is the world’s most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers-including the fastest-growing startups, largest enterprises, and leading government agencies-are using AWS to lower costs, become more agile, and innovate faster.
    #reInvent2022 #AWSreInvent2022 #AWSEvents
  • НаукаНаука

Комментарии • 7

  • @jasonhunter1786
    @jasonhunter1786 Год назад +1

    When changing primary regions with DynamoDB Global Tables, how do you know when all writes to the primary have propagated to the new primary? Is the answer different between (a) when all regions are healthy and it's a scheduled change vs (b) when the primary has perhaps gone fully dark or appears degraded? Thanks!

  • @yutakaobi9767
    @yutakaobi9767 11 месяцев назад

    Why not use global accelerator instead? Maybe less operationally expensive?

  • @rebdawi2002
    @rebdawi2002 Год назад

    What if GOaST goes down?

    • @barrysheward981
      @barrysheward981 Год назад +7

      First, in terms of keeping GOaST up, it is deployed across multiple regions, uses a DynamoDB Global Table and (as John suggested) we upgrade a region at a time. Second, when GOaST responds to the GMRlib, it not only provides current state, but also future state. The microServices using GMRlib can continue to run and even manage a primary rollover without GOaST. Finally, we can script sending state to GMRlibs if necessary.

    • @rebdawi2002
      @rebdawi2002 Год назад +1

      @@barrysheward981 That is brilliant :) Thanks

    • @evgenyminkevich6587
      @evgenyminkevich6587 Год назад +1

      @@barrysheward981 Thank you for sharing this - awesome talk.

    • @kulveersinghdhanoa
      @kulveersinghdhanoa Год назад

      @@barrysheward981 Are you planning to open source generic version of it ?