DEV Community

Adomas S
Adomas S

Posted on

Q: How would you structure project code?

Note: new here at, and couldn't quickly find a similar post/thread

How would you structure project code? (I'm talking mostly about directories here)

I mainly work in web development with React, but I have worked on multiple project in varying size and longevity.

One thing that always annoys me is when I see, what I call, (maybe there's a proper word for it) MVC architecture (explained below). The (only?) other way of structuring code is with what I call Feature based architecture, which I think is far more superior.

"MVC architecture"

Enter fullscreen mode Exit fullscreen mode


Enter fullscreen mode Exit fullscreen mode

It's when code is structured by layers and in my experience structuring code in this way have two main issues:

  1. Hard to find related code - if I'm trying to pin down code for a specific logic and start at views/PostActions.code I will be lucky if the code I'm looking for is in models/PostActions.code, but most of the cases PostActions will have multiple actions which will do different things in model layer, good luck finding it by names alone.
  2. Collaboration and code reuse - If I need to do something new in views/PostActions, I'll look there, and will only see code related to it's view, but when adding new code I'm less likely to find a model/Something, which I could reuse and not re-implement.

Feature based architecture

Where code is structured by logical parts or domains if you will.

Enter fullscreen mode Exit fullscreen mode

I find this way better since it's easier to see the whole code that is related to the post, which greatly reduces both issues I mentioned in "MVC architecture". If code needs to be reused it can be extracted above post which will indicate that this file can be used in all files "bellow".

What do you use?

So, let me know what you think of these? Are there any other way to structure code? Which you prefer? And do you even care?

Top comments (0)