Architecture of a Modern Javascript Web Application (Node.js & React)

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

In the next videos, we'll dive deeper into each of these topics so you can learn how to build your own web app.

Рекомендации по теме

Комментарии

Amazing, I just wished you didn't stop doing these vids.

chirilaandrei

Great! Thanks for taking the time to make this series of tutorials!

ChristopheHartwig

Man, I have been learning react for the last month. I come from an express vanilla background.
I was trying to code a modular blog website... kinda wordpress without the graphical admin interface and only with one percent of the functionality :D
My codebase is so cluttered, I am super impressed just skimming through your code in this video! It's just so clean!!

I mean my code is so messy that my mom just started throwing slippers at me!

johannsebastianbach

Really liked your video. The tools you use are almost exactly the same as mine. Also the architecture is very similar to my past projects. However I think I've found a better way.

For example the physical file hierarchy. 'controller, models, api''.. etc. Is very abstract. It does not tell the reader the intent of the system. When I was using that structure, I found my self jumping around the system quite a bit just to develop a single single feature. I'd have to update the controller, then switch to an entirely different folder hierarchy to update a model, then and update the server api, etc. Over time it slowed my speed, It make it difficult to add or remove features as systems greew because they were so spread out in the system.

So I tried a different approach. I started grouping code by use case, rather than by the category of the code tool. For example instead of grouping all the controllers together in the same folder, I created use-case folders where each use-case has its own controller.

For example there is one folder called 'user_login' which contains all the code for a typical user logging in. It still has a controller, a model and an api for routing etc. But from a coding point of view, it is much more efficient. Everything that changes together stays together.

One might argue that you lose the code-reuse opportunities with this method. For example you would have duplicate code for two different types of user-login. admin_user_login and normal_user_login might have the same user model. But that's why we have abstract classes. just pull what is common between the two user models into a file called abstract-user-login.js and have both use case models extend it.

chriskerley