Nodebestpractices: Structuring project by components - any real examples?

[erezhod]

Hi @goldbergyoni!
First of all, let me say thank you for sharing this amazing knowledge base, helps a lot.

I'm trying to re-structure a project that I'm currently working on for a client (Enterprise one) and it's a RESTful API using Node+Express which is currently structured the "classic" way (models, controllers, routes, etc...).

I tried following what you and the contributors mention here but I cannot seem to actually understand how to isolate components that far - kinda lacks more examples.

Are there any live code examples that demonstrate this methodology?

Thanks a lot! 🙂

[syffs]

It would make sense to have a full sample (or even a starter) project implementing most of the guidlines described here.

[goldbergyoni]

Are there any live code examples that demonstrate this methodology?

@erezhod I don't have something self-explanatory but should I hold a (free obviously) webinar in December will you join?

@syffs Yeah, you're right. Just don't have the time... Have many parts of these practices spreaded around customers projects but need few days to assemble all of them together

[erezhod]

@erezhod I don't have something self-explanatory but should I hold a (free obviously) webinar in December will you join?

Of course!

[syffs]

It would make sense to have a full sample (or even a starter) project implementing most of the guidlines described here.

In the same spirit, there's this repo, but it apparently does not implement all the best practices mentioned here.

For instance, the app is well layered, but by technical roles (models, services, jobs), not by components.

[MickaelNeves]

There's a very basic starting point here I guess.

[syffs]

There's a very basic starting point here I guess.

@MickaelNeves this is only my opinion, but I don't think this is an example anyone looking for best practices should follow:

• it is way too basic to provide enough material for structuring an app
• it's not well layered or structured: business logic is arranged in a very questionable way in api/resource folder

@goldbergyoni imo, all these different approaches and interpretations well demonstrate the need for a full featured sample. My feeling is that this repo is an educated starting point that would be decent relayered by component with a few tweaks.
Any thoughts ?

[MickaelNeves]

@syffs ok, so...

based on Uncle Bob's Clean Architecture, here's an example of NodeJS and here's an example with NodeJS + Mongo + Express.

[Stayfi]

Hi,

I want to share my repository about clean architecture with Typescript, express as Web
If you could have a check abd give me feedback about my "Uncle Bob" clean architecture implementation.

https://github.com/Stayfi/clean-architecture-ts

This schema show how i implemented it.

[syffs]

@Stayfi once again this is only my opinion... I think that this "architecture" introduces way too much complexity for the value its adds.

I'd say keep it simple !

If you pay attention, that's one of the main purpose of the architecture best practices described in this repo... For instance, why layering your app ? Simply because it breaks your app into simpler and smaller pieces easier to understand. Luckily, it also separates concerns which will also greatly improve your dev scalability.

[stale[bot]]

Hello there! 👋
This issue has gone silent. Eerily silent. ⏳
We currently close issues after 100 days of inactivity. It has been 90 days since the last update here.
If needed, you can keep it open by replying here.
Thanks for being a part of the Node.js Best Practices community! 💚