nodeshift/nodejs-reference-architecture resource
The Red Hat and IBM Node.js Reference architecture. The teams 'opinion' on what components our customers and internal teams should use when building Node.js applications and guidance for how to be successful in production with those components. observed · 2026-08-28
Health v2 · maintenance only
40/100
- Activity 17
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 2242
- days_rel: n/a
- days_push: 498
- n_releases_24m: 0
Adoption not part of the score
1747 stars · 123 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
The Red Hat and IBM Node.js Reference Architecture is a curated set of opinions and guidance on which Node.js packages and components to use when building applications, maintained by engineers from both companies. It documents recommended choices across functional areas like web frameworks, databases, authentication, and message queuing, along with production success guidance.
Use cases
- choosing which node.js packages to use for a new backend project
- getting production guidance for node.js applications
- finding recommended web framework for node.js services
- deciding on authentication and database libraries for javascript backends
- aligning team standards on node.js component choices
- learning how red hat and ibm build node.js apps in production
When to choose
- starting a new node.js backend and wanting opinionated, battle-tested package recommendations
- standardizing component choices across an enterprise node.js team
- seeking guidance validated at scale in large javascript deployments
When to avoid
- you need formal vendor support for the recommended components
- you want an exhaustive neutral comparison of all javascript ecosystem options
- you need frontend component recommendations, which are a planned follow-on
Facets
learning-resource · maturity active
developer-tools web-framework database auth message-queue logging configuration-management web-development backend developer-tools documentation cross-platform nodejs reference-architecture best-practices red-hat ibm opinionated-guidance production-readiness javascript-ecosystem
2 sources
- readme: https://github.com/nodeshift/nodejs-reference-architecture · fetched 2026-08-28 · c0819e638156
- homepage: https://nodeshift.dev/nodejs-reference-architecture/ · fetched 2026-08-29 · b257c2b7b1a7
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| nodeshift/nodejs-reference-architecture | main | 40 |
For agents
markdown · JSON · MCP: product_card(name="nodeshift/nodejs-reference-architecture")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem