Shulou(Shulou.com)06/02 Report--

This article mainly introduces "Why migrate from GoLang to NodeJS". In daily operation, I believe many people have doubts about why they migrated from GoLang to NodeJS. The editor consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful to answer the questions of "Why migrate from GoLang to NodeJS"! Next, please follow the editor to study!

At the beginning,

Let's start from scratch, starting with the back-end stack that contains GraphQL,PostgreSQL and GoLang. Our engineering team initially had only two people-one at the back end and the other at the front end, in charge of our iOS application. When I joined the team, the two engineers had left behind a lot of backstage problems.

ORM is not used, so the database is explicitly queried. The query written is too inefficient, we have been hitting the memory limit, and we have encountered a long wait time before the query is satisfied. This code has no architecture, it's a complete mess of code, and there are files everywhere. GoLang does not use the GraphQL library. Obviously, the previous back-end engineers tried to vanilla completely, and if you want to expand quickly, this is not an ideal path.

GoLang itself is not the problem.

None of these issues are specific to GoLang, but were introduced by an engineer who is not qualified for GoLang. This brings a problem for our startups: there are few GoLang engineers and even fewer capable engineers. We found ourselves hiring and firing two GoLang engineers who both tried to fix our backstage problems, but without success. Competent engineers are very expensive and far exceed the budget of our young startups.

As a startup, we are trying to bring the MVP version of the app to market, which means we need speed. The small set of libraries available to GoLang and GraphQL plus a small community means that we are solving problems at a slow pace. In addition, we are inexperienced with GoLang, and we spend more time solving problems than building functionality. The application itself is bound to become more complex, which means that this situation is not sustainable in the long run. We need an alternative.

Migrate to NodeJS

At some point, we sat down to discuss rewriting the backend. We need to solve the following problems:

We need a qualified back-end engineer at a fair market price that our startups can afford.

We need a back-end stack with many prefabricated solutions to common problems for quick migration.

We need a back-end stack with enough resources to solve some less common problems as we approach complexity.

Our decision is to replace GoLang with NodeJS. This solves all our problems, and the core of these problems is speed and cost.

NodeJS has a larger engineer market than GoLang.

Experienced NodeJS engineers are much cheaper than GoLang engineers.

NodeJS has many existing packages to solve common problems, allowing us to focus on building our applications rather than fixing them.

All in all, our decision to move to NodeJS depends largely on the state of our startup's business. People often argue about whether NodeJS or GoLang is suitable for your project, depending on the technical merits of the project, while our project boils down to why it allows us to move from prototype to MVP in a reasonable time.

At this point, the study on "Why did you migrate from GoLang to NodeJS" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.