If the database is unavailable and you are retrying, won't you be endlessly processing the same messages? Will all 500 go to the DLQ?
Golang
Tell me about yourself.
When does the Garbage Collector run? Are there specific stop points or moments?
You took a batch of 500 messages from Kafka but cannot save it to the database. What will happen? How long can you process these 500 messages?
What algorithm does the Go Garbage Collector use? How does it work in general?
Which synchronization tools from the list have you used in your project?
If we add many consumers but Kafka lag still does not decrease — what does this indicate?
How was the rate limit set? What was it based on and where was it implemented? What was used technically?
You mentioned the net amount — is that the salary or the total income?
Are DevOps and an analyst the same person? Was he a data analyst or a full-stack, system/business analyst?
What are you interested in doing? Am I correct in understanding that you mentioned Go's concurrency under the hood — is that specifically about an interest in the Go language because of its concurrency model?
How exactly was the message marked as a duplicate? Where exactly did this marking occur?
What types of gRPC interactions have you used? Can you name them?
What tasks would be interesting to solve?