State of Node

[SachaG]

Let's discuss what a "State of Node" survey would look like.

[plouc]

Potential topics:

• Hosting
  • Cloud
  • On premise
• Deployment (terraform, ansible, puppet, …)
• Run
  • Logs
  • Metrics
  • Monitoring/Alerting
  • Diagnostics (usage of APMs, async hooks adoption)
• Database
  • SQL
  • NoSQL
  • Graph
• Queuing
• CLI applications
• Registry
  • Private
  • Mirroring
• Security
• Node.js version
  • Used
  • Upgrade strategy
• Protocols (http, websockets, udp, …)
• Preferred learning resources
• Architecture
  • micro-services
  • monolith
  • Serverless/FaaS
  • …
• Development environment (OS, Docker, vagrant, …)
• Testing
  • Unit tests
  • Functional tests (BDD, …)
  • Load testing (gatling, tsung, …)
• Caching (varnish, redis, CDN, …)
• Add-on APIs and around native C/C++ modules building

[csantanapr]

For Architecture or backend add “Serverless/FaaS”

[csantanapr]

Add “develop Desktop Applications/BrowserlessApps” (electronjs, vscode, atom, Slack, etc..)

[lirantal]

Thank you for signing-up for this @SachaG!

I would like to lead and expand on the Security part. I'd like first to bring it up with the Security WG to figure out what what are some of the questions we'd like to explore.

There will be some interesting topics that Node.js members would like to figure out as well that we need to add to the list:

• Promises (practices, callbacks, async/await, etc)
• Diagnostics (usage of APMs, async hooks adoption)
• Add-on APIs and around native C/C++ modules building

Lastly, I'd like to ask to be involved in the organization and curation process if that's ok.
Me and @bnb would really be happy to.

[plouc]

Maybe "Promises (practices, callbacks, async/await, etc)" is more suited for StateOfJS.

[SachaG]

Also would this be "State of Node" or "State of DevOps"? A lot of things mentioned here aren't especially exclusive to Node after all.

[plouc]

There's already a "State of DevOps" by puppet.

[lirantal]

Definitely focus on Node.js

[bnb]

Just seeing this for the first time! Sorry, I have a really hard time keeping up with GitHub notifications.

Totally see where you're coming from with the question around "State of Node.js" vs. "State of DevOps". It's an extremely valid question.

From my experience working at a company that built Node.js specific monitoring and security tooling for two and a half years, there's... definitely a big difference. While a lot of the things listed above could fall under either "JavaScript" or "DevOps", Node.js is a beast because of its breadth.

The majority of DevOps-ish tooling focusing on polyglot approaches rather than having a really good Node.js experience. As such, those who are participating in the ecosystem that Node.js is underpinning have a really hard time getting information that's directly relevant – rather than tangentially relevant – to them.

Additional areas we could consider:

• Package Management
• Production Environment
• Ecosystem Generalizations
  • What is the overall state of documentation?
  • What is the overall state of tutorials/guides?
  • ...
• Assistive Tooling
  • Do you use transpilers (TypeScript, Babel, etc.)
  • Do you use bundlers (Webpack, Parcel, etc.)
  • Do you use a linter (Standard, ESLint, etc.)
  • ...