跳至內容

AppSync deployment downtime

1

A customer is asking whether there is downtime of AppSync service during deployment? they are using Cloudformation, for example, there could be schema update where new features are added with new resolvers, during creation of new resolver and schema update, would it affect existing AppSync service?

已提問 6 年前檢視次數 792 次

2 個答案
0
已接受的答案

No downtime unless you're making a destructive change (i.e. deleting resolver or data source").

AWS

已回答 6 年前

專家

已審閱 3 年前

  • I have a problem that there is a downtime between removing a resolver then replacing it with another resolver, is there a solution for the downtime here?

0

It should be noted that while update operations do not have downtime, they are also not instantaneous. There could be a short amount of time (a few minutes) after performing an update where the function or resolver is still using the old code. Consider the following scenario:

  1. AppSync resolver v1 points to lambda function v1
  2. A new release is created and deployed and thus the AppSync Resolver is updated to V2 and the lambda function is simultaneously updated to v2 (both update commands return ok)
  3. Request for the AppSync resolver are being handled by V1 for the next ~1 minute. If lambda function V2 is not compatible with resolver V1, there could be issues
  4. AppSync infrastructure finishes propagating the V2 changes and all requests are handled by the V2 resolver

So although the AppSync update API call looks like it returns completed in step 2, there are asynchronous activities by the AWS backend which may cause the changes to AppSync to not become active for some time. The time between 3 and 4 above could be a number of minutes during which any requests to the AppSync API from consumers could have unpredictable responses.

AWS

已回答 2 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。