A server that forgets everything the moment it restarts isn't much use. Almost every real application needs to store data (users, orders, posts) and get it back reliably. A database is where that data lives, and data modelling is the work of deciding how to structure it so it stays easy to query and hard to corrupt.
You'll start with SQL, the language used to talk to relational databases, then look at PostgreSQL, one of the most popular relational databases in use. From there you'll see two alternatives that fit different jobs: MongoDB, which stores flexible, document-style data, and Redis, a very fast store often used for caching. Knowing when each one fits is as important as knowing how to use it.
With somewhere to store your data, you'll be ready for the next module, Building & Consuming APIs, where you'll connect the frontend to your server and database with REST and GraphQL.
A quick introduction to SQL, the language for creating, reading, updating, and deleting data in relational databases, and how tables relate to each other.
A short look at PostgreSQL, a powerful open-source relational database, and what makes it a popular choice for production applications.
An introduction to MongoDB, a NoSQL database that stores data as flexible documents instead of rows and tables, and when that approach makes sense.
A fast overview of Redis, an in-memory data store commonly used for caching and other jobs where speed matters most.