# Single module vs. submodules in a project **URL:** \ **Category:** New to Julia\ **Tags:** performance, modules, code-organization\ **Created:** [February 15, 2021, 11:23pm UTC](https://discourse.julialang.org/t/single-module-vs-submodules-in-a-project/55361 "2021-02-15T23:23:33Z")\ **Posts on this page:** 1\ **Showing post:** 17

**Author:** ![MA\_Laforge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ma_laforge/32/385_2.png) [@MA\_Laforge](https://discourse.julialang.org/u/MA_Laforge)\ **Post date:** [February 16, 2021, 11:59pm UTC](https://discourse.julialang.org/t/single-module-vs-submodules-in-a-project/55361/17 "2021-02-16T23:59:27Z")

> [@erans](#): > > Thanks for all the tips, regarding this specific point though, my main interest _currently_ is the best way to structure code. My thought was, that the “best” way would likely best leverage Julia’s capabilities. As far as I can tell, the two main Julia highlights are JIT and multiple dispatch. With that in mind, I was/am trying to figure out how my code structure can best play nice with these concepts. If that’s the case, I suggest you take a look at my post here (and those it links to): > [@How to load a module from the current directory?](https://discourse.julialang.org/t/how-to-load-a-module-from-the-current-directory/21727/6): > > I don’t think this particular behaviour is documented yet. If it is, it wasn’t visible enough for me to find it: I as well struggled with this issue a few months ago. The confusion In particular, I had to look through Julia’s code to understand that any entry in LOAD\_PATH, whose directory contains a Project.toml file, will be treated as a “project environment” only. In other words: having a Project.toml file inhibits Julia from using it as a “package repository”. An introduction, for now At … --- _[View the full topic](https://discourse.julialang.org/t/single-module-vs-submodules-in-a-project/55361)._