Are you sure? I don't see any conflicts. I would say that the "nodebestpractices" focus on different things than Santiago. Actually I only find these 2 points comparable to the advice given here:
1.1 Structure your solution by components
1.2 Layer your components, keep Express within its boundaries
This is very general advice. Santiago follows this advice, but goes way further and fills it with practical instructions.
But his structure is not by components - but by roles. He has a models folder that holds all components models and services with all components services, instead of having a componentName folder with the respectable model and service.
This architecture is completely different from this one
github.com/i0natan/nodebestpractices
why would you say yours is better?
Are you sure? I don't see any conflicts. I would say that the "nodebestpractices" focus on different things than Santiago. Actually I only find these 2 points comparable to the advice given here:
1.1 Structure your solution by components
1.2 Layer your components, keep Express within its boundaries
This is very general advice. Santiago follows this advice, but goes way further and fills it with practical instructions.
But his structure is not by components - but by roles. He has a
models
folder that holds all components models andservices
with all components services, instead of having acomponentName
folder with the respectable model and service.Oh yes, the good component base architecture, that's a good way to do it too!! :)
better is not the right question, because every architecture has a purpose... what fit yours?