My Bulletproof NodeJS API Architecture
ฝัง
- เผยแพร่เมื่อ 9 ก.พ. 2025
- I landed a full-stack software engineering job with no degree, no bootcamp, and while living in a small panhandle town called Amarillo, where there is little no to opportunities for developers. Despite the odds, I made it happen. In fact, I went on to win first place in a coding championship before securing my job.
Now, I help others do the same. If you’re interested, join here: www.skool.com/...
Looking for a community to fast-track your success in software engineering and master web development? Join my community! Its free!: www.skool.com/....
Giving away free 1 on 1 coaching where I build personalized roadmap for you to become a software engineer, and I help you build a complex project! A total of 5 hours of coaching for free! Only for the next 30 people that sign up! :
www.skool.com/techascend/about
Very informative! Keep it up!
Thank you so much!!
Great
@@raghbirsingh8585 thank you!
Very informative. You earned a sub 😉
Thank you! I really appreciate it! I am just starting out my channel
Are you a dev? Or learning to become one?
@@daniel-guillen-1 full time dev bro.
This is what i call over engineering
@@bhanusharma2363 100% understand your point, what does your structure look like?
@@daniel-guillen-1 I think your approach is great but it is only applicable on a very large project. Most of the times projects are not that large in node js.
@@daniel-guillen-1 it will become harder to maintain over time
@@bhanusharma2363Gotcha! I agree with you, I think we should find a balance between over engineering and simplicity
However I believe the only way to find it is to test different architectural designs
do you have a github link for this?
Not yet, but I’ll work on it and make it!
Come back in a day or so and I’ll have it!
github.com/djg3577/NODEJS-BulletProof-Foundation
Here is a GitHub link! I will also attach to the bio of the vid
Note: This is just the backend template as shown in the video!
Too general, lacks clear separation of concerns, and can lead to scalability issues as the app grows, making it harder to maintain and organize. For instance, controllers and services may sometimes be intertwined, making it hard to manage responsibilities clearly.
@@sherry6892 totally get what your saying! I try to make the distinction between as much as possible, and has worked well for me so far!
What architecture do you recommend? Would love to hear!