> centralized system [... for errors] dont think this will scale. errors are part of API. (especially Go mantra errors are values https://go.dev/blog/errors-ar

> centralized system [... for errors] dont think this will scale. errors are part of API. (especially Go mantra errors are values https://go.dev/blog/errors-are-values https://go.dev/blog/errors-are-values it is ever more prominent). and each API is responsibility of a service so unless you deal with infrastructure or standards/protocols layer (say you define what HTTP 500 means or common pattern for URL paths in your API), then better not couple all services. those standards are very minimal and primitive that works for everything, which is opposite what you doing here aggregating all the specifics into single place