Plan Databases module restructure

[adamblanchard]

Context

There has been quite a bit of discussion surrounding the current databases module on the planning doc. Read the comments here.

Description

Databases is currently split up between foundation and backend in the above proposal. A few questions still exist:

1. Does this split make sense as it is?
2. If not, what are some required changes or additions?
3. While we don't want to reinvent the Databases module in this task, are there any other changes that we should really consider introducing at this point. e.g. there is a discussion whether we include nosql or not.
4. How does what we plan to teach and where influence what's possible in the final project? (somewhere where databases is often a big source of struggle for the trainees.

Comments from the original proposal:

• Maybe we should also include basic insert, update, delete in the foundation module
• Add in a “intro to databases” session where we cover the concept of storing data, data models in real life, and give a much better introduction to why we use databases and their role in the overall system
• Avoiding diving into nosql and focus more on SQL?
• Consider postgres over mysql, based on industry adoption and more up to date support for e.g AI features

Outcome

• A documented plan of how we split up the existing Databases module, along with any required changes.
• Shared for feedback in #curriculum-crew, and any other mentors you know who have experience teaching the databases module.

Pull requests or tasks

• [FOUNDATION] Update databases lesson material #63
• Review Intro to Backend - Database Exercise
• #6 chore: database foundation pre read #98
• Update database lesson material (Backend) #92
• Review DB setup in https://github.com/HackYourFuture-CPH/hyf-project-template/tree/main
• (Add more if needed)

[marcorichetta]

I can take on this task since I asked some of the questions in the document and offered to find an alternative to installing MySQL. I also think that could be a task in itself.

Thinking quickly:

• Keep NoSQL concepts but remove the practical content - https://docs.google.com/document/d/151MLm-8WA6jSk0-9JhBTuG1xZ9Fo9HRLplJx6Bhps6A/edit?disco=AAABgIUX3aQ
• Evaluate SQLite or some free DB as a service instead of having to install a database
  • If installing one, try using PostgreSQL instead of MySQL (This is based on popularity but no real changes on the basic concepts)
• Review existing PRs https://github.com/HackYourFuture-CPH/databases/pulls?q=sort%3Aupdated-desc%20is%3Apr%20is%3Aopen

[adamblanchard]

@marcorichetta we haven't fully planned what final projects will look like yet (in terms of tech stack, deployment options etc.) but what we teach in DBs should best reflect that, I imagine.

Right now, this is the template we have used for the final projects. I think it would be good to check in there what it requires.

We could also update that template, if we decide to do something differently. But we should keep them aligned, at least.

[marcorichetta]

@marcorichetta we haven't fully planned what final projects will look like yet (in terms of tech stack, deployment options etc.) but what we teach in DBs should best reflect that, I imagine.

Right now, this is the template we have used for the final projects. I think it would be good to check in there what it requires.

We could also update that template, if we decide to do something differently. But we should keep them aligned, at least.

Thanks for pointing that out Adam! I've never seen this content before.

At first glance, I'm thinking about using SQLite locally and PostgreSQL when deploying, avoiding Docker or other additional software.

In my head, this sounds good because:

1. locally they can configure their API by pointing to SQLite (connection string == DB file path)
2. when using the PostgreSQL database in Render, the string is changed to what Render displays

The code shouldn't change too much since Foundation uses basic SQL, and the final project uses Knex, which abstracts the DB interaction.

[marcorichetta]

14 may 2025 | Databases Restructure - Sync

Asistentes: Marco Richetta kristofferlocktolboll@gmail.com saloumeh@hackyourfuture.dk magda.zelezik@gmail.com

Notes (Context)

What:

• Working (for 2 months now) on restructuring the curriculum content

Why:

• Adapting to new tech trends
• More modular content
• Students can only study Foundation and decide whether or not to specialize on Frontend or Backend

How:

• Splitting the curriculum in Foundation and then add specialisms for Frontend and Backend
• We’re trying to maintain most of the legacy content

When:

• New content will be taught to the next team in Aarhus (Application process starts mid-summer)
• Priority: Foundation should be ready first

Related content

• Magda
  • Feedback as a recent DB mentor
  • Lesson notes

Next steps

• Use this issue to track all changes to Databases content
  • Create a sub-issue to update Backend Databases
  • Create a sub-issue to update Databases content in the Final Project
  • Ideally, there will be a few issues. You can always create another issue if it gets too large.
• I will finish adapting the Databases Foundation skeleton in [FOUNDATION] Update databases lesson material #63
• Magda will update the pre-class preparation content.