Moved to https://dmitri.shuralyov.com/blog/18.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[user] | |
name = DUONG Phu-Hiep | |
email = [email protected] | |
[core] | |
autocrlf = true | |
editor = code | |
precomposeunicode = true | |
ignorecase = false | |
excludesfile = | |
[alias] |
When designing or learning about APIs or microservices, it's crucial to consider error handling. API's designer often categorize errors into "Technical" and "Functional" (or "Business") errors. However, this distinction may not make sense:
- An API/micro-service should alway return ONLY "Functional" (or "Business") errors.
- The API/micro-service migh crash while processing a consumer's request and so the consumer will naturally get a technical error. But the API/micro-service should not deliberately return a "Technical" error for consumer.
We will explore the distinction between "real technical errors" and "fake technical errors," which are initially technical but later manifest as business errors, thus becoming "fake technical errors."
- HTTP 404 Business error (or Fake technical error)