nodejs/nodebestpractices
1
0
Fork 0
mirror of https://github.com/goldbergyoni/nodebestpractices.git synced 2025-10-29 00:19:14 +08:00
Code Issues Packages Projects Releases Wiki Activity

Saved readme-general-toc-1.md with Dillinger.io

Browse Source
This commit is contained in:
Yoni Goldberg
2017-09-26 12:22:46 +03:00
parent 9715933f42
commit bb7c68f83f
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
readme-general-toc-1.md
View File

@ -24,13 +24,15 @@ Welcome to the biggest compilation of Node.JS best practices. The content below
<br/><br/>
# `Project Setup Practices`
## ✔ 1. Do something important
## ✔ 1. Structure your solution by feature ('microservices')
**TL&DR:** Monitoring is a game of finding out issues before our customers do – obviously this should be assigned unprecedented importance. The market is overwhelmed with offers thus consider starting with defining the basic metrics you must follow (my sug
**TL&DR:** The worst large applications pitfal is a huge code base where hundreds of dependencies slow down developers as try to incorporate new features. Partioning into small units ensures that each unit is kept simple and very easy to maintain. This strategy pushes the complexity to the higher level - designing the cross-component interactions.
**Otherwise:** You end-up with a blackbox that is hard to reason about, then you start re-writing all logging statements to add additional information
**Otherwise:** Developing a new feature with a change to few objects demands to evaluate how this changes might affect dozends of dependants and ach deployment becomes a fear.
<br/>
🔗 [**Read More: Structure by feature*](/sections/errorhandling/asyncawait.md)
<br/><br/>
## ✔ 2. Do other thing