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

In this issue, Xiaobian will bring you about the use of moving from Node.js to Go platform. The article is rich in content and analyzed and described from a professional perspective. After reading this article, I hope you can gain something.

Easy to code across platforms

One of the biggest reasons we switched to Go was that it was so easy to compile code for different systems.

At Bowery, we're building an app that helps you and your team manage your development environment, and we have to efficiently support all operating systems-Linux, Windows, and OS X. In Go, you can define different files for different operating systems to implement OS-dependent functionality. A great example is our colleague Larz building a package Prompt that reads user input from the command line. Larz wanted to create a Go package to implement cross-platform line editing hints. This is so simple in Go: create different files for each operating system, and the Go compiler chooses which files to use to generate the final content based on the operating system.

Compiling code for other systems is also easy; all you have to do is set an environment variable and you have a Windows binary that you compiled on Linux.

faster deployment

Go is a compiled language and makes it easier to distribute apps across multiple platforms. Deployment and testing are important to us and an asset to our end users. With Go, it's easy to build services and run tests because you'll be ready when you migrate to a production server. Go doesn't require any system dependencies, making it really easy to release. When it comes to delivering command-line tools or other applications, our users don't have to worry about installing Java,RVM or NPM to run. We love this article by Jeremy Saenz, who discusses why he migrated all his command-line tools to Go(CLI tools to Go).

concurrent primitive

When we switched to Go we realized that Node.js 'event loop isn't everything. Node.js doesn't provide many concurrency primitives. The only things that can run simultaneously are I/O programs and timers, etc. You can't communicate through these programs, so building an agile system with Node.js is a challenge. With Go, you can run arbitrary programs while providing a channel to signal programs to do something, or to send them values to share data. Go also provides low-level concurrency primitives like mutexes, wait groups, etc. Some you might find on NPM, but we found that channel is the deciding factor when dealing with concurrency and parallelism.

Integrated Test Framework

With Node.js, we already had our choice of testing frameworks, but some worked better for the front-end, like Jasmine, and others worked better for the back-end, like Mocha. There are other options like JSUnit and PhantomJS, and if you read StackOverflow's article, there are also many frameworks recommended there. In some worlds, choice is a good thing, but with Go, we like the standardization of the test framework. In Go, all test packages are built-in. If you need to write a new test suite, what you have to do is add the (filename)_test.go file to the same package as the software you want to test, and it will run every time you execute go test.

You can learn more about Go testing at writing tests with Go. Need to test HTTP services? Go also provides httptest packages

standard library

We like to be able to write most software using only Go's standard libraries. With Node.js, we almost always have to introduce an external library, which increases both deployment time and potential vulnerabilities from third-party software. Using only standard libraries allows us to write code faster and safer.

More powerful workflow tools for developers

Node.js There is no real standardized workflow except for NPM packages and script controls. Besides, because these tools are community-created, they work well but there are so many of them that the end result is that things are done differently by everyone. A good example of workflow standardization in Go is workspace layout. You give up a lot of development freedom because you have to follow the layout of the workspace, but it provides a lot of structure: you can keep your Go source code and dependencies in the same place. You have three root directories in your workspace: src for source packages, pkg for compiled packages, and bin for executable programs. It is a best practice to keep your source code and dependencies in a separate workspace and make it standard on everyone's machine. These predictability are desirable in teamwork. We can go to anyone's machine and help, knowing that our code will appear at $GOPATH/src/github.com/Bowery instead of at $HOME/some/path/to/Bowery. Similarly,gofmt formats everyone's code in the same way. For superficial issues like code organization and code style differences, there is no need to worry about them in Go, which is a big liberation. You can focus on fixing your problem, everything else is taken into account.

There are a whole host of other reasons to like Go, and we're seeing more and more companies adopting Go to make their internal applications more powerful and distributable. But overall, the Go team has found that developers are more productive if you create standards and make examples that others agree with. For example, MongoDB's app management team likes to use Go's "smart, unified development experience." At Soundcloud, they like Go's strict formatting code rules and "there's only one way to do it" philosophy. This means you spend less time reviewing code and arguing about style and formatting, and more time addressing the root cause of your problem.

The above is a small series for everyone to share from Node.js to Go platform what is used, if there is a similar doubt, may wish to refer to the above analysis to understand. If you want to know more about it, please pay attention to the industry information channel.

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.