Menu

Fifteen outside services can be down, and our code has five different answers
📰

Fifteen outside services can be down, and our code has five different answers

DEV Community: nextjs·Daniel Pertu·4 days ago
#PHq6zD4f
#devtonextjs#devto#dev#error#catch
Reading 0:00
15s threshold

Nakodo is an outreach app for brands. Counting generously, fifteen things outside our own code have to be working for all of it to work, and on any given day one of them is not.

I went looking for the policy. There is no document, no circuit-breaker library, no resilience.ts . What there is instead is 139 catch blocks and 43 .catch() calls in non-test code, each one written in a hurry by me, at the moment I was holding the problem. This post is the audit of all of them, grouped by what they actually do.

The short version: there are five answers in the codebase, two of them are exact opposites, and one dependency has no answer at all.

You can see one of the five in the served HTML without signing up for anything. This is the sign-up form:

$ curl -s "https://nakodo.app/login?mode=signup" | grep -o "Checking you're not a bot" Checking you & #x27 ; re not a bot

Enter fullscreen mode

Exit fullscreen mode

That string is the label on a disabled button.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.