Re:From a Ruby monolith to microservices in Go
by Argorak on Wednesday March 04, 2015 @02:33AM
(#9143133)
As I said below, if you tread off the full-stack-track, you get a lot of the go-like things in Ruby as well.
My point being: I usually rate architectural changes as more important as a change in development details (and the programming language might be a big one there, but it still is one, IMHO).
I'll tell you why: a lot of the sentiments people bring when they now switch from Ruby to Go, I've heard before. When people started Ruby - I was already doing Ruby for ~2 years before Rails even came out at it got me into the position of saying: "just you wait until you see the bad parts". They attributed a lot of things to Ruby, while they were really changing their development model.
Only risk is, you break things into many component then you should so balance is required.