i use almost an identical approach, it would be great to have this folder structure and a bit of code to understand the logic behind it in a github repo! very nice analyze, you got a subscriber with a ringbell activated :)
I typically implement a DAL (Data Access Layer) to mediate between a service and a database in my architecture. Within the model layer, I maintain class definitions that represent database entities, which I refer to as entity models. My approach can be seen as a sort of 3.5-layer architecture, as the model layer doesn't have direct communication with the database. 🙂 Anyhow, thanks for explanation.
I think you're implementing something like Respository patten, in that case, the ORM you use should'nt apear in the service layer. Instead, you use the ORM in the repositories, then you call its functions in the services right ?
Would have loved to be able to see this repository and investigate the routes, services, controllers etc in more detail. Thank you for the great video nonetheless!
Make a video upon how to do testing, unit testing etc. And also best practice to implement logs. Superbbbb content dude. I was looking for this from sooo long. Up for any support if needed.
Could you show us how to properly deploy a microservices architecture like this with several services and monitoring service to AWS or some other cloud proviiders? I think it'd be a great video
This video should really be a playlist. It would be great if you slowed down and gave some specific examples for each of the major points. It seems like your target audience is new Node developers, but you move way too fast for them to keep up with you.
Could you apply Design Patterns, like Strategy, in node projects like the one in the video, with router, controllers and services? I´ve seen it and applied it in Java projects, but with POO paradigm. So, i´m in doubt if it is a good practice or not, to use it in node projects with this kind of paradigm.
what about the repository pattern ? the repository can contains only the db interactions using the ORM (ODM) like mongoose. in this case, you should NEVER use mongoose in the service layer, because it's only for writing the buisness logic!
Video was super helpful! I'd love to see a tutorial where you make a simple api from start to finish showing how to correctly use the 3-layer approach
Thanks! I’ll try to follow that pattern in future videos 😉
NestJS provides a seamless implementation of the 3-layer architecture. I recommend using it for anyone not wanting to re-invent the wheel.
Great video. Thanks so much! Second or third time that I'm watching it. Appreciate it!
For this reason i really love to use Nestjs. Which is using 3 layer approach. And also you can have modules for each different tasks.
Good point!
i use almost an identical approach, it would be great to have this folder structure and a bit of code to understand the logic behind it in a github repo!
very nice analyze, you got a subscriber with a ringbell activated :)
I couldn’t really go into code due to time constraints but thank you for the feedback 😉 And happy to have you here!
Can you attach the github repo?
For Logging and Debugging, I use Morgan and Winston. The best part is you can combine it together to have the best o/p.
Amazing explanation, I'm here trying to learn more about architectures in backend due to I'm a Frontend trying to understand more about backend logic.
Excellent! Nice layout and simple to read code. Unusual on TH-cam vids 🙂
I typically implement a DAL (Data Access Layer) to mediate between a service and a database in my architecture. Within the model layer, I maintain class definitions that represent database entities, which I refer to as entity models. My approach can be seen as a sort of 3.5-layer architecture, as the model layer doesn't have direct communication with the database. 🙂 Anyhow, thanks for explanation.
Interesting, thanks for sharing :)
I think you're implementing something like Respository patten, in that case, the ORM you use should'nt apear in the service layer. Instead, you use the ORM in the repositories, then you call its functions in the services right ?
Would have loved to be able to see this repository and investigate the routes, services, controllers etc in more detail. Thank you for the great video nonetheless!
Make a video upon how to do testing, unit testing etc. And also best practice to implement logs.
Superbbbb content dude. I was looking for this from sooo long.
Up for any support if needed.
Will do, buddy. Thanks for the nice words! 😊
Could you show us how to properly deploy a microservices architecture like this with several services and monitoring service to AWS or some other cloud proviiders? I think it'd be a great video
Great suggestion!
Very helpful vidoe of node developers.
Glad to hear that!
Glad I'm following the same folder structure. 3layer structure 😅😅
This video should really be a playlist. It would be great if you slowed down and gave some specific examples for each of the major points. It seems like your target audience is new Node developers, but you move way too fast for them to keep up with you.
Great suggestion, will keep it in mind!
Thank you for sharing!!
That was informative for sure
Hey! Thanks for the video😍. Can you please share the folder?
Please do a video on monorepos!
Already have one! 🙂
really good content
Hi I wish I could access that project example in github.
Do you really need a separate model layer when you are using an ORM like sequelize?
Can you share microservices/serverless/SOA/monolith folder structure
I’ll consider those in future videos 🙂
Thank u ❤
Could you apply Design Patterns, like Strategy, in node projects like the one in the video, with router, controllers and services? I´ve seen it and applied it in Java projects, but with POO paradigm. So, i´m in doubt if it is a good practice or not, to use it in node projects with this kind of paradigm.
good explaine next content please Go-lang :)
Ohh I'd first need to learn Go :D
Love your videos man. What tool do you use to make these boards
It’s Excalidraw :)
it would be great to complete this with `Analytics`, `Continuous Integration (CI)` and `Deployments (staging/production)`
Good point!
I have class based routers and controllers and models are seperate...I generated them using sequelize cli
If anyone has a good source for learning this, please share it in the comments.
can u share the codebase link in the description?
Why you separate controllers and router? Can't they be the same thing?
They could, but it’s easier to work with separate files, once the number of endpoints gets too large
@@SoftwareDeveloperDiaries ok understood
what about the repository pattern ? the repository can contains only the db interactions using the ORM (ODM) like mongoose. in this case, you should NEVER use mongoose in the service layer, because it's only for writing the buisness logic!
Hello, Do you still got the repo for this?
Did you mean that the best structure is a nest?
I agree :)
can you share the repo of this project
Unfortunately there's no code for this one :/
any example repo??@@SoftwareDeveloperDiaries
We want to read your code 😊
FYI...sounds like you might have some kind of automated video or audio editing, seems to cut off some words in parts of your videos
Exactly, it’s a feature in Filmora that removes silent parts of the video :)
@@SoftwareDeveloperDiaries Sounds like it needs tweaking because its removing parts of words, possibly a gate setting.
is it possible to get this project source code?
Unfortunately not for this one, sorry 🥲
I wish you could share the code for your videos
I will do my best to do that in the future videos!
good video. sorry for changing 666 thumbs up to +1 )) but I can't just pass by
huseyin baskan r harflarini cok vurgulu soyluyorsun dinlemek yorucu oluyor. haberin olsun. basarilarinin devamini dilerim
😒 'promosm'