I want my site to always be up because I want people to be able to use the information on the site. If the site is not up, the information can’t be accessed to be used.
I haven’t benchmarked my site because it doesn’t get enough traffic to impact the load on mv VPS. My load average right now is 0.00 0.00 0.00.
Benchmarking is a useful tool, as demonstrated in my recent post Concurrency Slower?. Benchmarking Go or Apache doesn’t make much sense to me because your application or use case will always be different. I think a better approach is to instrument your application and then use that data to figure out where there are performance problems. Once a problem is located, benchmarks are useful for making sure the changes you make to the code actually improves things.
Using Let’s Encrypt with go is easy. Here is an example. I use a cache with the manager to avoid generating new certs when my server restarts/updates.
On another note, you aren’t “definitely behind”. There’s nothing to “catch up” on. Sure, there are things you don’t know. There will always be things you don’t know. In fact, the more I know, the more I know I don’t know. What I try to do is know about many things so that I can learn them as needed. For example, I was able to respond to your other post because I remembered I had seen a package that could help; then I had to find it so I could share it with you.
Running your own git server does not need to be difficult. If you are the only one who needs access, then a VPS with ssh access works well. If you need to manage multiple user, then something like Gogs would be easier. Just make sure you have backups handled.
To quickly get started writing web apps in go, you might like a book like Web Development with Go: Learn to Create Real World Web Applications using Go. The author, @joncalhoun, also runs a website and email list with beginner-appropriate material. You might, however, prefer some other book of the many available.