I heard that go is not very suitable for writing services with a lot of business logic, what is your opinion?

Question

go

I really want to hear a detailed answer why go is not suitable / suitable in this situation.

Answer 1

Because go is a rather low-level language with a minimum of abstractions and no generics.

Answer 2

May be

Answer 3

In general, it’s worth starting with the fact that the concept of “with a lot of business logic” is quite extensible. If we talk about microservices, then they usually have a lot of business logic and it doesn’t work out. Because if this starts to happen, then you should think about whether there is no extra responsibility in the microservice? Perhaps this service should be divided into smaller ones?
A bit from personal experience and not quite on the topic of the question, you never know it will come in handy. I was writing microservices in go and noticed the following shortcomings (for me personally):
Pros:

1. Strong typing
   
2. Compilation result - one binary
   
3. Pretty interesting bug forwarding (many people don't like it, I liked it)
   
4. High speed
   
5. Low memory consumption
   
6. There are flows
   

Answer 4

Yes

Answer 5

Not

Answer 6

So Go is no longer suitable for anything.

Answer 7

It all depends on the developer. You can use Go, while implementing most of the business logic in SQL queries, for example.