Over the last 3 years our teams here at Red Hat and IBM have worked to present the team's guidance on building Node.js applications for the enterprise. This guidance comes from the experience the various teams had when interacting with our customers. Select sections of the reference architecture were included in our multi-part blog series.
Based on the analytics, we have been very fortunate to have such a positive response to the work we did. This allowed us to put together an E-Book based on our blog series:
Getting Started
For those that haven’t heard of the Node.js Reference Architecture, there is a great overview post that introduces you to the blog series:
A goal of the reference architecture was to cover a wide range of components based on the experiences of the team. This was accomplished by breaking down those experiences into 3 main categories. Below are the top rated posts for each of those categories
Functional Components
These are the things that make a Node.js application a Node.js application
- Introduction to the Node.js reference architecture, Part 6: Choosing web frameworks | Red Hat Developer
- Introduction to the Node.js reference architecture, Part 8: TypeScript | Red Hat Developer
Development
These are things that a developer should be thinking about while developing their Node.js application
- How to build good containers in Node.js | Red Hat Developer
- 8 elements of securing Node.js applications | Red Hat Developer
Operations
These are things that a developer will be using and monitoring when their application is deployed and being used.
- How to investigate 7 common problems in production | Red Hat Developer
- Our advice for the best Node.js logging tool | Red Hat Developer
Conclusion
As always if you want to learn more about what the Red Hat Node.js team is up to check these out:
https://developers.redhat.com/topics/nodejs
https://github.com/nodeshift/nodejs-reference-architecture
https://developers.redhat.com/e-books/developers-guide-nodejs-reference-architecture
