MVC (Model-View-Controller) is a popular design pattern for organizing your code. In this tutorial, we organize our Express REST API with MVC. In addition, we complete the CRUD operations for our simple JSON data. If you are just starting out with Node.js & Express, you may want to start at the beginning of this Node.js for Beginners playlist found here: th-cam.com/play/PL0Zuz27SZ-6PFkIxaJ6Xx_X46avTM1aYw.html
@@DaveGrayTeachesCode Sorry, Dave, my english is ugly a little bit, and I wrote my comment in russian (my native language). And also I want, let you know, you have fans in Russia! I often send links to your channel to my IT friends.
Beside organizing the code, what I really like about MVC design pattern (or alike) is that we can separate the code facing the outside world (controller) from other codes dealing directly with the data (model), regarding createEmployee handler, getting a new id by incrementing the last employee id will work fine as long as our data is sorted by id (which is the case here), but if we for some reasons have the data unsorted or sorted by something other than id then I think it cold be better to find the max id + 1 anyways, using a real database engine IDs can be auto generated, for the unsortedArray.sort function, although it's much clearer this way but it can be made shorter by returning a.id - b.id (I think you mentioned this in a previous video but don't remember where) Thanks Dave for keeping us thinking
Thank you very much. In this lesson (after copy-pasting your source code) - Thunder Client doesn't respond to requests While the server runs on port 3500. It did work during the Router video (where I manually wrote anything you did).
There must be some difference as I do not have that issue here. I might suggest using git clone instead of copy & paste. You can download my source code repositories with git that way.
Hi Dave, cool node+express series, as well as a channel in general, I love the way you explain details. Can you advise if there is some balance between the amount of code in Routers and Controllers? I'll explain a bit. I had 90% of all my code directly in the Routers, inside the "(req, res) => {}" functions, I thought the code would work faster, neglecting the convenience of writing, refactoring, etc. I had literally thousands of lines of code in my routers. Recently I've redone everything and transferred all my code to the respective controllers. However, I believe, there should be some balance between the two. A lot of similar imports in my controllers make me think about some sort of inefficiency. I came from very ancient languages like Assembler, Basic, Pascal, etc. :)) where repeating was treated as something very bad and inefficient, even an extra semicolon was bad)) not to mention entire models or other controllers. The logic behind was really simple - the compiler will bring all the imports into 1 file anyway. I realize that the browser does not compile JS))) however, the entire chain ends up on hardware anyway... Thus I'm wondering about your approach, experience, or even thoughts in this regard, thank you in advance.
I took a small brake because the Course became very advanced. It is hard to progress building the project at the same time when it is at the beginning level. Now I am practicing very basic "Express JS Crash Course" by Traversy Media youtube channel, but I am coming back soon, and surely I will finish it.
Hi, I'm wondering whether I should be using immutability for my functions or not(I've done mine without and tested it out and it seems to be working fine), additionally using immutability consumes more data storage from what I know, and for a larger amount of data that could come into play, afterall im updating the existing database always and not creating a new one so it shouldnt be required but maybe its better viewed or actually is better in some other way or maybe I'm supposed to use it interchangebly depending on each case? Thank you for your great videos
I have a question on part 14:20. When you run employee.firstname = req.body.firstname, wouldnt it mutate the existing employee object in the existing array? In that case isnt it unneccesary to remove the object from array and add it again?
Good thoughtful question! You are receiving an employee object from the find() method that was called. It is stored in a new variable named employee. We are updating the object held in the employee variable. It is not in an array. It does not mutate the pre-existing object in the database. We then filter the employees array (not to be confused with the employee variable) to remove the old employee object and replace it with a new one.
@@DaveGrayTeachesCode I am sorry for asking again. But what I meant was that find() method will give an employee object, but it is the same object in the data.employees array. The variable name employee is just a pointer to that existing object in the array. Yes, as you said it doesn't mutate the pre-existing object in the database, but it should mutate the object in data.employees array.
@@skyhs0168 right ! true that coz employee variable will be referencing the object from the array and thus any changes made to it will appear in the array as well
Hi, Dave! First of all - thank you for all the great tutorials! I have a question about response data transformation. Should it be done in the controller layer or should there be an additional "service" layer between the controller and the model? Thanks!
You're welcome! 💯 Either could work. The data is often transformed by middleware which is essentially what a service layer would be before it reaches the controller.
Hi Dav, Grate tutorial, Thank you for that. I have a question we have different libraries for API development expressJS, NestJS many more can you suggest me which is best for a realtime steaming application which should read data from a data bricks server continuously
You mention some specific requirements here that I don't feel I have enough experience with to give an opinion on which is *best* . You can usually achieve your goals with multiple solutions so I would define _best_ as the one you are most familiar with.
You are almost reading my mind! Authentication is the next thing I wanted to add to this Node & Express series before moving to database options. I'll focus on the backend, but a separate tutorial could do the frontend in detail, too. 💯
@@DaveGrayTeachesCode Thank you so much!!!! I will be on the lookout! It's my third year as a programmer I haven't been able to scale that part of my learning curve. and I have not had access to quality tutorials out there
One thing appears to me looking your great video. Having separated 'routes' and 'controllers' layers you should avoid use of http related APIs inside the controller. It should not be coupled to any platform and contain only business logic. Controllers should be easily portable to desktop GUI app and should have nothing to web/http staff. All data passing from web layer and http interaction should be handled by 'routes', and your routes are pretty "dumb" passing all the logic (even web handling one) to controller.
For sorting the array in ascending order with respect to employees' id in the updateEmployee() function, it would be better the usage below. Just as a recommendation. data.setEmployees(unsortedArray.sort((a, b) => a.id - b.id))
MVC (Model-View-Controller) is a popular design pattern for organizing your code. In this tutorial, we organize our Express REST API with MVC. In addition, we complete the CRUD operations for our simple JSON data. If you are just starting out with Node.js & Express, you may want to start at the beginning of this Node.js for Beginners playlist found here: th-cam.com/play/PL0Zuz27SZ-6PFkIxaJ6Xx_X46avTM1aYw.html
Я лайкаю все новые видео сразу же. Ибо результат всегда на высоте гарантированно! А потом уже смотрю, когда есть время. Большое спасибо!
Thank you! I needed to use Google translate to understand, but I appreciate your message! 🙏💯
@@DaveGrayTeachesCode Sorry, Dave, my english is ugly a little bit, and I wrote my comment in russian (my native language). And also I want, let you know, you have fans in Russia! I often send links to your channel to my IT friends.
@@cradleofkaschenko2057 thank you so much! You can continue to comment in Russian. I think Google does a good job translating. 💯🚀
Thank you so much Dave :). This course has really made my transition into backend easy and interesting 🤝
Beside organizing the code, what I really like about MVC design pattern (or alike) is that we can separate the code facing the outside world (controller) from other codes dealing directly with the data (model),
regarding createEmployee handler, getting a new id by incrementing the last employee id will work fine as long as our data is sorted by id (which is the case here), but if we for some reasons have the data unsorted or sorted by something other than id then I think it cold be better to find the max id + 1
anyways, using a real database engine IDs can be auto generated,
for the unsortedArray.sort function, although it's much clearer this way but it can be made shorter by returning a.id - b.id (I think you mentioned this in a previous video but don't remember where)
Thanks Dave for keeping us thinking
Thanks Ahmad! Great notes here my friend. 🙏💯
Спасибо!!! Отличный канал, прекрасный педагог! Успехов!
Thank you!
you're an amazing teacher!! thanks for sharing this tutorial and keep doing them!!!
Thank you! Will do! 🙏💯
Thank you very much.
In this lesson (after copy-pasting your source code) -
Thunder Client doesn't respond to requests
While the server runs on port 3500.
It did work during the Router video (where I manually wrote anything you did).
There must be some difference as I do not have that issue here. I might suggest using git clone instead of copy & paste. You can download my source code repositories with git that way.
It is beautiful to see it's working..
interested way to explain everything was amazing to understand ...well explantion thank u
Can we just use sort((a, b) => a.id - b.id) instead of sort((a, b) => a.id > b.id ? 1: a.id < b.id ? -1 : 0) in updateEmployee when sorting the array?
Yes, same thing and simpler! 💯
Thanks Dave, great work !
You're welcome! 🙏
Hi Dave, cool node+express series, as well as a channel in general, I love the way you explain details. Can you advise if there is some balance between the amount of code in Routers and Controllers? I'll explain a bit. I had 90% of all my code directly in the Routers, inside the "(req, res) => {}" functions, I thought the code would work faster, neglecting the convenience of writing, refactoring, etc. I had literally thousands of lines of code in my routers.
Recently I've redone everything and transferred all my code to the respective controllers. However, I believe, there should be some balance between the two. A lot of similar imports in my controllers make me think about some sort of inefficiency. I came from very ancient languages like Assembler, Basic, Pascal, etc. :)) where repeating was treated as something very bad and inefficient, even an extra semicolon was bad)) not to mention entire models or other controllers. The logic behind was really simple - the compiler will bring all the imports into 1 file anyway. I realize that the browser does not compile JS))) however, the entire chain ends up on hardware anyway... Thus I'm wondering about your approach, experience, or even thoughts in this regard, thank you in advance.
Excellent reference as always!! Thank You Dave….
You're very welcome, Gordon 🙏💯
Great tutorial! I learned something new. I really appreciate the explanations
You're welcome, Patrick! 💯
I took a small brake because the Course became very advanced. It is hard to progress building the project at the same time when it is at the beginning level. Now I am practicing very basic "Express JS Crash Course" by Traversy Media youtube channel, but I am coming back soon, and surely I will finish it.
Thank you Piotrek. I understand and fully support learning at a pace you are comfortable with. 💯
Hi, I'm wondering whether I should be using immutability for my functions or not(I've done mine without and tested it out and it seems to be working fine), additionally using immutability consumes more data storage from what I know, and for a larger amount of data that could come into play, afterall im updating the existing database always and not creating a new one so it shouldnt be required but maybe its better viewed or actually is better in some other way or maybe I'm supposed to use it interchangebly depending on each case? Thank you for your great videos
Thanks for your hard work bro.
You're welcome! 🙏💯
I have a question on part 14:20. When you run employee.firstname = req.body.firstname, wouldnt it mutate the existing employee object in the existing array? In that case isnt it unneccesary to remove the object from array and add it again?
Good thoughtful question! You are receiving an employee object from the find() method that was called. It is stored in a new variable named employee. We are updating the object held in the employee variable. It is not in an array. It does not mutate the pre-existing object in the database. We then filter the employees array (not to be confused with the employee variable) to remove the old employee object and replace it with a new one.
@@DaveGrayTeachesCode I am sorry for asking again. But what I meant was that find() method will give an employee object, but it is the same object in the data.employees array. The variable name employee is just a pointer to that existing object in the array. Yes, as you said it doesn't mutate the pre-existing object in the database, but it should mutate the object in data.employees array.
@@skyhs0168 right ! true that
coz employee variable will be referencing the object from the array and thus any changes made to it will appear in the array as well
@@baxtables yes it does mutate the object in the array.
6:49 how we handle put and delete to this path without dinamic paramethar like :id?
I liked very much
Keep up
Thank you, I will! 💯
Great tutorial on getting started with Express using the MVC Pattern. Thanks, Dave
{2022-06-10}
You're very welcome! 💯
So good tutorial thank you
Glad it was helpful! 🚀
Thanks!
Thank you for the support! 💯
Hi, Dave! First of all - thank you for all the great tutorials!
I have a question about response data transformation. Should it be done in the controller layer or should there be an additional "service" layer between the controller and the model?
Thanks!
You're welcome! 💯 Either could work. The data is often transformed by middleware which is essentially what a service layer would be before it reaches the controller.
@@DaveGrayTeachesCode Thank you for the prompt reply!
Hi Dav, Grate tutorial, Thank you for that. I have a question we have different libraries for API development expressJS, NestJS many more can you suggest me which is best for a realtime steaming application which should read data from a data bricks server continuously
You mention some specific requirements here that I don't feel I have enough experience with to give an opinion on which is *best* . You can usually achieve your goals with multiple solutions so I would define _best_ as the one you are most familiar with.
cool
Could you please upload a video that explains authentication; like how to consume a signup and a login endpoint with Javascript or react? thanks
You are almost reading my mind! Authentication is the next thing I wanted to add to this Node & Express series before moving to database options. I'll focus on the backend, but a separate tutorial could do the frontend in detail, too. 💯
@@DaveGrayTeachesCode Thank you so much!!!! I will be on the lookout! It's my third year as a programmer I haven't been able to scale that part of my learning curve. and I have not had access to quality tutorials out there
🚀
One thing appears to me looking your great video. Having separated 'routes' and 'controllers' layers you should avoid use of http related APIs inside the controller. It should not be coupled to any platform and contain only business logic. Controllers should be easily portable to desktop GUI app and should have nothing to web/http staff. All data passing from web layer and http interaction should be handled by 'routes', and your routes are pretty "dumb" passing all the logic (even web handling one) to controller.
why u make video ?????
For sorting the array in ascending order with respect to employees' id in the updateEmployee() function, it would be better the usage below. Just as a recommendation.
data.setEmployees(unsortedArray.sort((a, b) => a.id - b.id))