[djb_hackernews]

It sounds like you are building a transactional CRUD webapp that doesn't need to scale all that much, for a startup where the team already has a bunch of experience with Rails, which IMO, has the best ecosystem for webapps available (and I'm not a huge Rails fan.) And the main reason you are looking at Golang is because of performance improvements, even though it doesn't have a great ecosystem yet, never mind a solid webapp framework, and the team doesn't have much experience with it? Is that right?

Having written and maintained a large Rails app from the ground up, and done some small projects in Golang, I think you'll be extremely dissatisfied with all of the extra work you'll find yourself doing, which really takes away from the time of actually getting your product in your users hands.

When coming from Rails, most other options will have speed that is tempting. If it were me and I were in your position and wanted to avoid Rails I'd pick Java/JVM for its speed, ecosystem and its fit in to fintech. But that's me. Or just use Rails and rewrite it in the new shiny if and when performance becomes a problem.

[tedmiston]

My startup's experience was similar. Our core is an Angular app to a Django backend API.

Django and Rails are roughly the same level of maturity.

The approach that's worked best for us is to keep all of the business logic and CRUD-y stuff in this Django base, then spin out dedicated microservices in the special cases e.g. CPU-bound tasks. I think most startups end up with a similar architecture.