Starting with Go
Go is boring in the best way possible. It's the closest thing to writing backend infrastructure that just works. The language is strict. The compiler is opinionated. And the standard tooling feels like it was written by people who actually built servers for a living.
Go doesn't try to be clever. You'll write more lines of code, but you'll also sleep better knowing that your app won't randomly choke under load.
What worked for us
- Fast compilation and fast runtime...
- Goroutines and channels make concurrency less terrifying.
- We could ship a single binary, copy it to the server, and it ran. No VM, no venv, no node_modules.
What made us roll our eyes
- Error handling is repetitive. There's a lot of if err != nil everywhere.
- Generic support is new and sometimes awkward.
- Some libraries are barebones. Expect to DIY a bit more.
Go shines when you care about performance and reliability. But yeah, it's a bit stiff compared to the others.
#Cloud#Architecture#DevOps#Microservices