Handling errors LIKE a 10x ENGINEER in Golang - Golang Service Pattern

In this video, I discuss handling errors when using the Service Pattern within Golang. Specifically, I talk about writing a generic service error package that can be used throughout your application to save from manually catching specific errors throughout your HTTP / gRPC / any other "adapter" your service may use.

This has personally saved me lots of pain with services that expose both an internet-facing HTTP endpoint and a gRPC internal method, saving me from having to write any code to convert errors to match the transport method.

Let me know what you think, and of course, let me know if you have any nice ideas on how you get around this problem in your Golang services.

[matthew]

Jesus dude I’ve been looking for Go content like this. I’m going to binge watch all your videos. Keep it going.

[MatthiasFasching]

I'm not a big fan of having the service decide which HTTP error the handler returns if something goes wrong.

Let's say we have a service that manages invoices and a method that returns a given invoice based on it's id. If that invoice doesn't exist in my opinion we should not return an error that is automatically mapped to 404 in a handler because depending on the context a 403 or even 5xx might be a better response.

Errors returned by services should be specific to the service and the handler should decide how to map those errors to HTTP status codes not the service.

[esra_erimez]

Most impressive. Not only was this video clear and informative, I can tell you know what your talking about by how fluid you are in talking about it. Well done.

[cole.maxwell]

So good! Thanks for being the senior I don't have

[hectorcast]

how do you handle db transaction in service pattern? like using 2 separate services in the handler function.

[rampandey]

Thanks for the video will implement it in a current project

[matthewrawlings]

This is a great pattern, I had recently just done something similar on a recent project

[Bashx]

Hey man, would you mind sharing your font and theme? Nice video. Thanks

[memeherp]

thank you, your channel make my go code more clean 😊

[TehGettinq]

I also end up doing similar stuff for generic-ish error handling. Sadly the only thing this truly highlight is how poorly designed go is.

[anhhaoam]

Where did you get the Join function? Because in errors there is no Join function.

[danimunf]

I'm kinda lost, why do you put errors.go under service? wouldn't it be more intuitive to put it under commons / helper? because it's the more generic error, am i right? thanka in advance

[konradpiotrowski]

Damn, this is nice. Imho it would be perfect if you finish it off with some dependency injection, specific error handler interface which is later on implemented by a few packages, http, grpc... So then when you switch from httperror to grpcerror you do it in one place by replacing the structure instead of refering to a different package everywhere :)

[gouravkolhatkar]

Mate we need full beginner friendly tutorial of go from you. Please 🚀❤.

[nooblero]

So much code and you are still going to end up with thousand lines of "if err != nill"
When people are asking for better error handling I am not sure that we worry about how to transfer error details, but rather how to make the code cleaner and less repetitive.

[oleksandr-petrovych]

get rid of the "SWITCH", it spoils everything