nodejs-reference-architecture - The Red Hat and IBM Node.js Reference architecture

项目说明

Node.js Reference Architecture

O

The goal of the Node.js reference architecture is to present
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.

Traditionally there has been reluctance to recommend a subset
of the packages the Ja ecosystem but our customers are increasingly
looking to the team for an opinion of where to start.

The components in this architecture are what we recommend to help internal
and external customers get started based on our experience. Other components may be equally
good, but these are the ones we know best and have the most experience with.

Where possible the opinion is based on what we've used internally and in our customer engagements.

The components specified will be our first priority for our contributions to open source projects in the Ja ecosystem.

Due to the abo are the components the team is best positioned when working with internal and external customers.

However, we do not include formal support for these components in any of our support offerings unless specifically identified
in those offerings.

The recommended components may change over time as technologies and approaches change.

If you want to learn more about some of the discussions that went into the Node.js reference architecture you can check out the Introduction to the Node.js reference architecture blog post series.

The team

The team consists of engineers from across groups within IBM and Red Hat who:

are actively engaged in the Ja/Node.js community

ha Ja/Node.js deployments

provide consulting advice and/or de related to Ja/Node.js for customers

develop/deli or Node.js components

Key tenets

Whene components should have been at scale within the team's

Ja/Node.js deployments or in engagements with our customers.

We need to consider licensing and other due diligence when selecting components.

We are going to start with a focus on the back-end, a similar effort for front-end

components will make sense as a follow on.

Components

The reference architecture covers the following components (currently a work in progress
with only a subset of sections having recommendations):

#### Functional Components

- Web Framework
- Template Engines
- Message Queuing
- Internationalization
- GraphQL
- Databases
- Authentication and Authorization
- Data Caching
- REST API De
- Load Balancing, Scaling and Multi-threading
- Consuming Services
- Node /images
- Transactions_handling

#### De

- Typical De Workflows
- Kubernetes-based De En
- Choosing and dependencies
- Building good containers
- Static Assets
- Protecting Code
- Code Quality
- Code Consistency
- Testing
- Code Co
- TypeScript
- Accessibility
- Cross Origin Communication
- CI/CD
- Npm
- Npm Proxy / Internal Registries
- Npm Publishing
- Package De
- Secure De Process
- Ser

#### Operations
- Monitoring
- Logging
- Metrics Collection
- Health Checks
- Distributed Tracing
- Problem Determination
- Failure Handling

Module Diligence

As a minimum, any modules recommended as part of this reference architecture should meet the following criteria:

The module is not deprecated.

The module has an appropriate license.

- Generally leaning towards permissi such as MIT - others should be re on case by case basis.

The module runs on LTS of Node.js.

The module has appropriate testing.

The module is appropriately maintained:

- Regular releases (where appropriate).
- Critical bugs reports are acknowledged and addressed.
- Reported security are patched and released.

Contributing

To Contribute to this project, please see the Contributing Guide.

Contributors

Anthony Whalley - Technology Partner Architect - IBM

Bethany Griggs - Sr. Software Engineer - Red Hat

Carlos Santana - Senior Technical Staff Member - IBM

Dominic Harries - Dev Lead at IBM Garage for Cloud

Jim Lindeman - Sr. Software Engineer - IBM

Joe Sepi - Open Tech Program Director - IBM

Lucas Holmquist - Sr. Software Engineer - Red Hat

Michael Dawson - Node.js lead for Red Hat and IBM

Noel Madali - Web Architect - The Weather Company at IBM

Tony Erwin - Senior Technical Staff Member - IBM

Wojciech Trocki - Software Engineer - Red Hat

项目信息

开发语言：JavaScript

Star 数：1749

技术要点

该项目属于红蓝攻防方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕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.展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

从技术实现角度看，此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论，梳理项目的初始化流程、核心模块职责与数据流转，逐步掌握其中的技术细节与设计思路。

使用与学习建议

1. 下载源码压缩包，解压到本地环境。

2. 根据项目类型准备对应的运行环境与依赖。

3. 按照 README 中的步骤完成配置与部署。

4. 在隔离的测试环境中运行验证，避免影响生产系统。

免责声明

本资源来源于开源社区，仅供安全研究、技术学习与合法授权范围内的攻防演练使用，请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。