I'd say it's more a monolith vs microservices post than a Rails vs Go one. I tend to agree with the conclusion: microservices are a waste of time in many contexts.
That was my take away as well. It seems like the authors biggest mistake was choosing a very complex architecture, and the remedy was simplifying into a single service using a framework the author was more familiar with.
Comments
I'd say it's more a monolith vs microservices post than a Rails vs Go one. I tend to agree with the conclusion: microservices are a waste of time in many contexts.
That was my take away as well. It seems like the authors biggest mistake was choosing a very complex architecture, and the remedy was simplifying into a single service using a framework the author was more familiar with.