Member-only story
Best Practices
How to Structure Your Application Code (The Easy Way)
Code organization often determines application comprehension and long-term maintainability.
You’ve noticed structuring code isn’t that easy. Starting from scratch often begs the question “where should this class go?”. Even the simple act of naming a solution, module, project, or what have you, can be mindboggling difficult.
It’s very likely you’ve already read tons of articles on this matter. You get different answers every time. This is great, as it broadens your repertoire of possible approaches, but, at the same time, it poses new questions. Also, having lots of options may even hinder your decisiveness.
“Enough, just show me the code structure!”
Great, you’re in a hurry, I get it. Here’s how I typically structure my code. This is useful for both enterprise-level applications as well as startups that want to hit the ground running, allowing for future flexibility without sacrificing agility.
Folders marked as bold.|src/
|- Core/
|---- Application project
|---- Domain project
|- Infrastructure/
|---- DataLayer project
|---- Other infrastructure projects
|- Presentation/
|---- WebApi
|---- Mobile App
|Tests/
|- Whatever test projects you have
|Scripts/
|- database.sql
|- pipeline scripts/templates (CD/CI)
|- ARM templates (Code as Infrastructure)
|Documentation/
There you have it. There’s really nothing more to it. But stick around if you want an explanation of each folder and the reasoning behind this structure.
Shameless plug.
Before we get into it…
Here’s a short youtube video that’ll go thru everything laid out in this article. I’ve just now decided to start a channel where I can upload videos of the subjects I’m writing about. If you’re more of a visual learner — I don’t know why you’d be reading this article then though.
