Well, it all depends on what you want to learn, but when I start a personal project this is what I usually do.
What backend language would you use?
Nodejs with express is my default to go. I'm familiar with it and it is really easy to set up.
What approach would you take with structuring the database?
I would choose a document store, like MongoDB, and have a collection for each kind of data I need to store, unless the data is highly relational, but that's seldom the case in my projects.
What approach would you take with structuring the application?
I start simple and let the structure emerge as I learn more about the application I'm building. My starting point is usually grouping vertical slices of functionality in the same folder. For instance, if I have an API related to users, I would have a user folder with separated files for the API endpoints, the database operations, and any other layer of functionality I might need.
Well, it all depends on what you want to learn, but when I start a personal project this is what I usually do.
Nodejs with express is my default to go. I'm familiar with it and it is really easy to set up.
I would choose a document store, like MongoDB, and have a collection for each kind of data I need to store, unless the data is highly relational, but that's seldom the case in my projects.
I start simple and let the structure emerge as I learn more about the application I'm building. My starting point is usually grouping vertical slices of functionality in the same folder. For instance, if I have an API related to users, I would have a
userfolder with separated files for the API endpoints, the database operations, and any other layer of functionality I might need.You can check this project on GitHub to see an example of what I mean.
This is awesome. Thanks, I'll check out the GitHub