Designing a clean REST API with Node.js (Express + Mongo)

preview_player
Показать описание

Рекомендации по теме
Комментарии
Автор

Here's a link to the article I mentioned in the video.

Elegant patterns in modern JavaScript: Ice Factory

DevMastery
Автор

You are the only one I found on Youtube who talks about architecture of an application! Million of bows!!!

logicjs
Автор

Good architecture is really about reducing the cost of future change. Love that.

timi
Автор

This video was an excellent resource. Just getting into Node and was trying to wrap my mind around how to keep entity models, routing, and custom logic layers distinct in such an open ended platform. This ticked all those boxes and also highlighted how to stay framework agnostic. Definitely subscribed.

jacobyoungblood
Автор

Hey, I just watched the replay from Barcelona. Amazing video, Bill! I really like how calm and clear your explanations are.

The topic for the architecture is right on the spot (at least for me). This is something that troubles me for long time and I still struggle to wrap my head around. I've been trying to implement the "Clean Architecture" by Uncle Bob but I have trouble designing the layers and connect them. Your video is very helpful and I feel I understand more :).

One important conclusion from watching your video is that, SRP (Single Responsibility Principle) is crucial to make things neat and organized. I see that you give objects different responsibility that is well encapsulated, provides an interface and all you need to use it is inject an object to generate some concrete output :). Beautiful!

I'm looking forward to seeing more content! Great work! Honestly!

PlamenAndreevX
Автор

Hi Bill, I really like this and the other video you made on clean architecture.


I've been coding for about 4/5 years now, mostly front end and this way of architecting an application is sorely missed in my learning so far!


Hungry to learn more now with as many practical examples as I can find! :)

MultiMarty
Автор

Your application architecture videos are the best I've ever seen. Most are either too abstract to be useful or too in the weeds with unimportant details. Here everything is presented perfectly. Thank you for sharing your wealth of knowledge/insight on the subject.

neilr
Автор

thank you so much for making these videos, you're one of the best and most informative teachers i've found on programming and web development!

SMasta
Автор

I just want to say thanks for doing this show. This particular episode kick started me down the clean coding path using Node.js. I was looking for a good example to get me started and this was exactly it. Kudos!

dantesta
Автор

The Ice Factory pattern seems very interesting! I think I'll start to implement it in a project I'm currently working on! :) Good job on the videos btw! Waiting for more :)

adrian.barylski
Автор

This is gold! Thank you and please keep uploading.

MauricioRobayo
Автор

This is the tutorial I was looking for. Thank you very much.

DUNIACARA
Автор

@Dev Mastery, many thanks for the video. There is some real, practical learning here. Can you show (or make a video) us how to deal with nested documents. let's take an example of Society/Property management db where there are many entities e.g. A residential complex -> wings -> floors -> rooms -> tenants -> more -> more . You can see there is a lot of nesting and the stuff can be real complex (at least to some of us). It would be great if you can also show us how to club together data from different documents which aren't related, as there may be similar use cases. Apologies if it's too much to ask.

thecodeclass
Автор

Excellent series! Really like the topics! I noticed in contact-list.js, you reference db.collection. Is "collection" a mongo client library function? What happens if I switch the DB object to Postgress? Will this still work or is the expectation that refactoring contact-list is ok in this when switching DB engines?

sparkman
Автор

I like the use of the pattern "function makeContact(contactInfo = requiredParam('contactInfo') {...}". However, it does not catch the case when contactInfo is null. Are you intentionally ignoring nulls (ie, consider it a programmer error) instead of checking for it and throwing an error?

dantesta
Автор

ject into makeContactList() to switch from mongo to something else? I see references to mongo inside makeContactList() as well.

dantesta
Автор

Thanks for these videos.

I have a request: If it's not too much to ask, do you mind leaving comments on your code so beginners like me could follow along even without the video?

Again, thank you very much.

oboiteosahon
Автор

wow, subscribed. i need more your video. please film more

jacsurfing
Автор

Great video. the architecture of the application is very interresting and very strong. But actually i'm thinking about the scalability of the code. how can I make the API evolve (create a version 2 while keeping the version 1) without duplication of code while maintaining the same design ?

EddyCaffrey
Автор

Hi ! I have studied OOPs during my college days but I started working on Javascript instead. Now I am heading to Typescript . Can you please adjust a lecture in which you can explain on how to conceptualise the major OOPs concepts like inheritance, interfaces, abstractions, etc in a real world project implementation. Basically I want to know how to think while working on Class based concepts.

ravinderrikhi
visit shbcf.ru