you should be able to apply the same principals you picked up from developing in Java/Closure node/js applications tend to be a bit more home grown than more t

you should be able to apply the same principals you picked up from developing in Java/Closure node/js applications tend to be a bit more home grown than more traditional, convention driven ecosystems for architecture: my "advice" would be to start with a single file, add things until you start to find friction (having multiple windows of the same file open is a good sign, constant searching too), break things into separate files based on your preference, folders and directories along the same lines, be consistent your knowledge and opinions about errors/exceptions is valid here too nodejs is fast but its not so much a performance focussed platform so ime, tuning options are lacking. there is an eco system of tools for managing stuff but it bleeds into the environment a lot more e.g. process management, ops and infra