3 ms·

Thank you all for the good responses on the error code issue. I particularly appreciate the ops view on this, e.g. the existence of much tooling around monitori

Thank you all for the good responses on the error code issue. I particularly appreciate the ops view on this, e.g. the existence of much tooling around monitoring HTTP codes. Since I'm a pragmatist I'm not going to defend my point of view too vigorously, but concede that there are other considerations, particularly when designing services to work at scale. Everything breaks at scale, including many things we believe to be wise and true :)

johnjuuljensen 10y ago
Context: Friendly banter >> Bottom line - your server should always return HTTP status 200 and a separate API error response. That is a very absolute statement from a pragmatic guy, asking people to concede viewpoints other than their own :) I'd be interested in learning how status codes other than 200 cause problems at scale though?