There are several reasons we've been using go for web backends where I work:
- Very easy deployment (we can just copy the same binaries between our 64 bit linux boxes and run them)
- Go's libraries for developing minimal web interfaces are excellent
- Being strongly encouraged to do all the explicit error checking made our Go code much more reliable and easy to debug than our previous python versions.
Of course, all of this depends on how big the project is. We just have several components of a project that require a simple webpage frontend with a small REST backend to interact with Redis. Our entire server for both the frontend and backend is ~1200 lines of Go and easy to understand. If your project is much bigger, you may end up needing features that aren't present in Go (as was the case with Dropbox), which may slow you down some.
- Very easy deployment (we can just copy the same binaries between our 64 bit linux boxes and run them)
- Go's libraries for developing minimal web interfaces are excellent
- Being strongly encouraged to do all the explicit error checking made our Go code much more reliable and easy to debug than our previous python versions.
Of course, all of this depends on how big the project is. We just have several components of a project that require a simple webpage frontend with a small REST backend to interact with Redis. Our entire server for both the frontend and backend is ~1200 lines of Go and easy to understand. If your project is much bigger, you may end up needing features that aren't present in Go (as was the case with Dropbox), which may slow you down some.