I have never worked on a project where the db being “down” was anything less than a catastrophe, as seemingly compared to a regular hiccup in this article.
The article just seemed to me like it does not focus on that error case because it's not interesting to the pattern.
You tell your client that the request failed and that's it, right? Or there's certainly other patterns designed to help avoid hard fails when the DB is down, but they seem orthogonal to this one, use them if they're helpful to your project, skip if not?
You tell your client that the request failed and that's it, right? Or there's certainly other patterns designed to help avoid hard fails when the DB is down, but they seem orthogonal to this one, use them if they're helpful to your project, skip if not?