nodejs/nodebestpractices
1
0
Fork 0
mirror of https://github.com/goldbergyoni/nodebestpractices.git synced 2026-03-13 08:40:16 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1259 from eltociear/patch-1

Browse Source 
Fix typo in readme-general-toc-4.md
This commit is contained in:
Raz Luvaton
2023-07-28 10:37:20 +03:00
committed by GitHub
parent c72f74aa3e 27032a913f
commit d3b764f7d6
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
sections/drafts/readme-general-toc-4.md
View File

@@ -25,7 +25,7 @@ Welcome to the biggest compilation of Node.js best practices, based on our check
## ![](../../assets/images/checkbox-sm.png) 1. Structure your solution by feature ('microservices')
**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.
**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. Partitioning 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:** 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.