News for hackers. Stuff that matters.

A comment on From a Ruby monolith to microservices in Go.

Re:From a Ruby monolith to microservices in Go by bobofettfett on Wednesday March 04, 2015 @02:27AM (#9143118)
If you move from Ruby to Go and this works better for you, then choosing Ruby in the first place might - if it was not about a prototype or getting VC money or only found Ruby developers - be a failure on your part.
[ Parent | on HN ]
Re:From a Ruby monolith to microservices in Go by pmontra on Wednesday March 04, 2015 @03:57AM (#9143322)
Ruby got them customers within the bounds of their time and money budget so it did its job. Nothing in the post suggests they have regrets about it but it would be interesting to hear from them.
[ Parent | on HN ]
Re:From a Ruby monolith to microservices in Go by nexneo on Wednesday March 04, 2015 @05:55AM (#9143587)
Without Ruby we couldn't have build lots of features with such a tiny team. We don't regret and we are not replacing Ruby entirely (just few parts)

85% of our server codebase is still Ruby.

[ Parent | on HN ]
Re:From a Ruby monolith to microservices in Go by bobofettfett on Wednesday March 04, 2015 @05:27AM (#9143521)
When Ruby can't solve your business problems -> wrong choice. If it can solve your business problems -> wrong choice to move to Go.
[ Parent | on HN ]
Re:From a Ruby monolith to microservices in Go by bobofettfett on Wednesday March 04, 2015 @05:44AM (#9143557)
Yes, couldn't read find that in the article beside "monolitic baeh"
[ Parent | on HN ]
Re:From a Ruby monolith to microservices in Go by grey-area on Wednesday March 04, 2015 @05:42AM (#9143549)
Requirements change.
[ Parent | on HN ]