| I've worked (as a freelancer) on a number of apps recently using Rails for the "front back-end" and either Erlang or Go for the "back back-end" and it's been working great. Rails works great for things like authentication, creating a nice and maintainable UI, handling billing code, sending emails, managing the database schema, and all the web related stuff. Erlang and Go work nicely for all the "heavy work", think sending tens of million of push notifications quickly, crunching data etc. They can communicate using a shared, Rails-maintained database, and things like Redis to trigger updates or orders. You can even do Erlang-backend processing of Sidekiq payloads, pushed from the Rails side etc. All in all: use each tool for its own strengths. |
Nothing that Go cannot do. The only difference between Go/web and Rails is the maturity of the libraries.
Of course Go libs are way less mature for various "business tasks".