Is there interest in the following topics: Refactoring, Architecture or System Design

[goldbergyoni]

Is there interest in the following topics: Refactoring, Architecture or System Design

[goldbergyoni]

Welcome aboard! These topics are highly relevant and important and at the same time, 'flamable' and debatable so should get handled with extra care.

The first section (project structure) deals with multiple architecture topics (e.g. microservices, screaming architecture, domain driven design), we definitely can include some wisdom from clean/hex (I personally don't appreciate MV*). For example, bullet 1.2 might include quotes from clean/hex that resonate why express should stay away from the domain

I'll be glad to see some related PR, maybe first before going to the distance share what you intend to add? Please take into account our content guidelines.

[goldbergyoni]

@TheHollidayInn any follow-up thoughts from your part?

[TheHollidayInn]

Sorry for the delay!

Reading over the first section again, it does seem to include the principals of good architecture without explicitly choosing. I'm going to cross reference my material to see if there is more I can add.

I would like to add bullet to section 4 with a summary of creating a plan to refactor and use a tool like CodeClimate as a starting guide. Would that be okay?

Maybe in section 1, 5 or 7 I could add a bullet about offload longer tasks to redis. I can find some examples/docs. From reading your guidelines I do see this Each advice should be related directly to Node.js and not to software development in general so I am trying to think about Nodejs specifics, but the System Design items might be more general and not fit in. Although it would be good if you develop APIs/Microservice systems to at least have a reference to the ideas.

[goldbergyoni]

@TheHollidayInn sorry for the delay, liked very much few of your ideas

Short intro - Everything, after all, is related to 'general sw development'. The main idea here is to write about topics where the nodejs interpretation/implementation are non-trivial with emphasize on the node related topics. The specific tools (e.g. redis, code climate) should not be the main topic rather the concept and the leading tools can be specified in the end

I find it a great idea (!) to write about static code analysis as part of the CI with emphasis on js/node related issues like avoiding over nested closures that increases the measured code complexit or any other interpretation of complexity analysis and node. Anyway, the tools (plato, code climate, sonarcube) shold be kept to last

Separating long-running, non customer facing, to external workers might also deserve a bullet but the implementation is highly controversial - I can think of 7 different techniques to achieve that. What for example can we write under this bullet?

[goldbergyoni]

Closing -> Moved to a PR