Reputation: 682
Is there a recommended architectural pattern for handling maintenance downtime in a system say on AWS? One approach suggested to me was to have a backup JSON file on an s3 bucket and fallback to that where the main API is down. Then have a /healthcheck end-point on the main API that the client could first check. The problem I have with this is that it requires the client to make several requests before getting a list of items or example. Is there a more opaque way of doing this such that the client wouldn't need to do anything? I'm thinking something along the lines of CloudFront redirecting to the backup JSON file on the s3 bucket when it gets a 500 from the origin?
Upvotes: 0
Views: 44
Reputation: 912
I think you can handle this with AWS Route53 and healthchecks.
You will need to transfer your domain to AWS DNS Service.
Upvotes: 1