Echo Application Architecture Best Practices Article

[ottothorntonsilver]

Hey All,

I recently wrote up a best practices article that outlines a layered/hexagonal architecture approach to structuring Echo API services. I'd be really interested to hear what you all think and get some feedback! Let me know what you think https://medium.com/@OTS415/structuring-golang-echo-apis-8d657de5dc7c.

Thanks!
Otto

[aldas]

I would recommend looking at this comment #2075 (comment) that second example with type users struct struct.
NB: that example is about DB but I would recommend creating services/repository abstractions and not access DB connection directly in handlers.

I do not recommend returning errors like that return c.String(http.StatusBadRequest, err.Error()) instead of that just return it or wrap and return. In that case middlewares can handle that error and global error handler can handle that error.

I do not recommend handling errors directly in handlers like return handleError(c, err). Use global error handler for that (e.HTTPErrorHandler =)

[martinyonatann]

i use this https://github.com/DoWithLogic/golang-clean-architecture