SaaS application architecture in Go (Golang-way)?

Question

go

Tell me how to build the architecture of SaaS applications on Go in general (Presentation Layer, Business Logic Layer, Data Access Layer). And also in particular for projects where background tasks, reports, etc. are constantly spinning (for example, applications of the Moody's rating agency).

Answer 1

You are too specific about the question, it was enough to write "how to write services?")) NOT the "correct" architecture (this does not happen), but the most suitable for the stack of possible tasks with the possibility of changing the requirements for business logic and scaling - you can write only if you have on the hands of TK + the budget is known. This applies to all EPs.