Piero Borrelli
Jul 5, 2023 ⋅ 10 min read

Node.js project architecture best practices

Piero Borrelli Fullstack developer. Passionate writer and content producer. Lifelong learner.

Recent posts:

Error Handling In Rust A Comprehensive Guide

Error handling in Rust: A comprehensive tutorial

Learn to handle Rust errors efficiently to write cleaner, more maintainable Rust code and create a more user-friendly application.

Eze Sunday
Jul 18, 2024 ⋅ 10 min read
Exploring Actions And Request Rewriting In Astro

Exploring actions and request rewriting in Astro

Astro v4.8 ships with server actions and request rewriting. Let’s see how to use these long-awaited (though still experimental) features.

Ivaylo Gerchev
Jul 17, 2024 ⋅ 13 min read
Comparing Fiber Vs Gin For Go Web Development

Comparing Fiber vs. Gin for Go web development

Go Fiber and Gin are two popular Go frameworks that provide extensive toolkits for developing high-performance apps with modern features.

Temitope Oyedele
Jul 17, 2024 ⋅ 8 min read
Leveraging Typescript Branded Types For Stronger Type Checks

Leveraging TypeScript branded types for stronger type checks

Branded types in TypeScript allow us to write code more clearly, provide more type-safe solutions, and maintain our code more efficiently.

Rashedul Alam
Jul 16, 2024 ⋅ 5 min read
View all posts

13 Replies to "Node.js project architecture best practices"

  1. Great article! Although I’m not sure I agree that you should use promises like that. The async/await style has worked very well for me.

  2. You’ve touched on some points of Clean Architecture, but you could take it even further by having an Application Context file that manages your dependencies that you need to inject. This also makes mocking for tests extremely easy.

  3. Rule #1: Correctly organize our files into folders
    Too obvious for most developers.

    Rule #6: Use dependency injection
    Its not true. It should be well-considered decision and depends on many factors, otherwise can make codebase hard to maintain.

    Rule #11: Always comment your code.
    Its not true. Good variables and functions names are self-documenting. In most cases comments just add noise and decrease code readability.

    Rule #12: Keep an eye on your file sizes
    Usually size is not a problem for server-side code.

    Rule #13: Always use gzip compression
    In general Its preferable to enable gzip compression on nginx, not in Node.js.

    Some points, like linting, code style, unit testing just dont relate to architecture, like article’s title says.

  4. Nice article,thanks for sharing.
    You have to correct the example “A simple basic example of a promise”, it will call both the resolve and the reject

  5. Looks like more of a general set of things you could use in a service rather than an actual guideline how to build a good architecture flow. Unfortunately, it’s possible to follow those and still have quite a bad architecture

  6. Dependency injection makes testing much easier. Combine it with Adapters for your vendor libraries/frameworks and you get a nice decoupled system that can swap dependencies with much less effort.

    It actually increases the complexity of codebase in order to improve maintainability IMO.

  7. Loved this article. As a junior Dev, this is gold. Can you please share any open source github project that is using this particular or a similar architecture so that I can see how its actually implemented in code? It would be very helpful. Thanks!

Leave a Reply