How I write HTTP services in Go after 13 years
1–10 of 259 posts
Re: How I write HTTP services in Go after 13 years
#2What is the value making main.go as small as possible?
Whose dreams come true in this scenario?
Re: How I write HTTP services in Go after 13 years
#3What is the value making main.go as small as possible? Whose dreams come true in this scenario?
The initialization has to be done in a separate function that you call from the setup code for your end-to-end tests.
Re: How I write HTTP services in Go after 13 years
#4What is the value making main.go as small as possible? Whose dreams come true in this scenario?
If you do, you can use the application as a library and most of your code will also be easier to test.
Re: How I write HTTP services in Go after 13 years
#5What is the value making main.go as small as possible? Whose dreams come true in this scenario?
Usually your main function can't be used by any other part of your program. You should move all component implementations to modules so they can be re-used elsewhere.
Re: How I write HTTP services in Go after 13 years
#6What is the value making main.go as small as possible? Whose dreams come true in this scenario?
“Whose dreams come true in this scenario?”
I love this! I will use this as well.
There are so many situations where I have a feeling that people are solving problems that don’t exist. In code I run into at work, code and projects I see online, etc
The “whose dreams are you making come true” really applies here, because dreams are exactly what they are.
I spent quite some time writing an automatic image resizer and optimiser for my blog. Does it matter? No! Should I have spent that time writing blog posts instead? Yes! Still I was chasing some dream.
Thanks for this image
Re: How I write HTTP services in Go after 13 years
#7What is the value making main.go as small as possible? Whose dreams come true in this scenario?
not main.go but func main. This allows your run function to return an error and you only need to deal with the abruptness of using os.Exit once
Re: How I write HTTP services in Go after 13 years
#8What is the value making main.go as small as possible? Whose dreams come true in this scenario?
For bespoke internal services, I like to keep main.go as flat as reasonable, like a "script". Handlers can have their own files but the bulk of the control flow and moving parts should be apparent from reading the main file.
Abstracting things away from main makes it less readable and is general pointless for bespoke services that will be deployed in exactly one configuration.
Re: How I write HTTP services in Go after 13 years
#9i really like the patterns in this post, pretty much what i've also settled on after much experimentation with different styles.
Re: How I write HTTP services in Go after 13 years
#10Great article with lots of interesting ideas. Can't believe I didn't know about signal.NotifyContext. Finally I'll be able to actually rememeber how to respond to signals instead of copy-pasting that between projects.