You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We accept Golang because it's go-routine is suitable to the usecase of a remote api client. There are many pause time to wait a returning a result from a remote server, and this application would require to spawn many threads to handle many incoming request and calls many remote api. For this purpose, Go-routine is very reasonable mechanism.
When we rewrite this, we thought node.js as alternative approach instead of Golang. It's async I/O model is also reasonable for our purpose. Then, however, we wont to focus simply deploying without Docker or other virtualization approach. We wont to deploy only the executable binary and a few configuration files. node.js requires many dependency modules into local's ./node_modules/ dir. We need to pack them into a tar ball before deploying it. It's not our requirement.
The text was updated successfully, but these errors were encountered: