Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    how short is very short? could you just delay the response a few ms? Commented Oct 7, 2021 at 12:38
  • @Ewan that's a good question. Actually, I think I made the wrong statement. We do have a retry process in place to consume from the queue. However, how long some event remains stuck in the queue entirely depends on how long we have trouble with DynamoDB. If Amazon does a good job, it should be short. I took a look at 1 year statistics, we have less than 300 events ever arrived at the fallback queue. Chance of failure is low but we want to use the same system for more services internally going forward. So I'm looking for a way to improve our promise to the clients. Commented Oct 7, 2021 at 13:37
  • I guess I worry when you start to try and fix something that your underlying system is supposed to do. If the write is always supposed to work but doesnt, will your remedy be any more reliable? Rather than write a fall back for "can't write to db for obscure reason" you might be better writing a "flip to Azure when AWS is down" for those times when something major goes down Commented Oct 7, 2021 at 13:47