So “use rails until you raise a C round?” heh

I'd say it's more use Rails for all of your standard CRUD operations and then use Go as a module in Rails using Quartz/FFI if you have any algorithms that need to be high performance. Of course you could always go down the microservice route and spin up a Python/Go service for your more intensive data processing modules.

Exactly, we use Rails for most of the functionality and Go for the functionality that gets used most.

Start with Rails and optimize in Go for the services that get expensive to run in Rails, like https://gitlab.com/gitlab-org/gitaly

I don't have any serious comment, but love "gitaly" as a project name.

if that was a pun on the C language, then I officially groan