Say you have a rails app, and you're already using queueing (resque) to offload some slow/non-urgent processing on the server. That queueing processing performs some functionality need for the rails app - and then saves information into a memecached store... Everything is good.
But is it possible to write a component triggered by queueing that runs a go application that, in turn, leverages the same underlying database as the rails app and writes to the same in-memory store?
Is this common? Not so trivial? The database schema would be familiar to both rails and go, and while the go app might have some duplication of business logic, it's pretty siloed. Think of it as a way to gradually migrate some server functionality running in rails to running in go. Is this done in practice?
