From node. js to Go, why one Startup made the Switch

This is a creation in Article, where the information may have evolved or changed.

At Gophercon, the Go conference this past April 24-26 in Denver, Kelsey falter, CEO and founder of Poptip, made the case F or choosing Go over node. JS for hers company S backend servers. Her stories are an example of a company choosing Go for their ability to excel at the systems level management. As for node. JS, there is numerous examples of the service was used in the enterprise. We'll explore how companies is using node. js in future posts about the new stacks that organizations is building. This was simply about one company and what it solved the challenges it encountered with node. js by turning to Go.

Poptip ' s problems with Node started about a years ago. Falter said she knew how to write JavaScript and thought she could use this background to learn Node. The speed of development made it easy-for-the-get started with Node. It had modern features such as WebSockets. It was also free and cost little to administer. The Node community had momentum, language homogeneity, and a talent pool.  At the time, it had that coolness factor, too. Here is her overall grades:

Poptip helps companies provide a statistical breakdown on public consensus. Its clients include CNN, L ' Oreal, Spotify, and a host of others. The size of these customers required Poptip to scale its code. Its service is depends on learning and streaming data.  As the company scaled, the task of administration became increasingly complex, due to "call-back soup", a common complaint With node. js. It is easy-to-get Node going, but Poptip's growth created a variety of problems, which falter described in her Presentati On

• Multiple application layers could not being brought up in tandem.
• The infrastructure had a single point of failure if the instances went down.
• All functions of the service ran in a single process.
• Latency became an issue due to high CPU and network load during peak usage.
• There was a inability to scale horizontally.

But why Go?

There came a point is the technical debt became too much, due especially to the scaling of the Poptip service. It was also a business decision:the company had received venture financing and there were customers to manage.

The switch came when one of Poptip's engineers spent a weekend replicating the core processing structure with Go. Text processing increased percent just by moving from Node to Go. Poptip formally evaluated Go,and it passed the scorecard Test:it had the runtime speed, the cost of administer was minima L, the talent pool was excellent, and competing frameworks were isn't vying for the attention of the developers.

Poptip started using Go with the app server and then ripped out the proxies, falter said. This is past fall, the company does the Web front end in Golang, as well.

Since adopting Go, Poptip have been able to scale their infrastructure in a manner not possible with Node.  is this Y Our experience? Did your company make the switch from Node to Go? Why?