Check: databases

Knowledge check · 5 min · Module 9, lesson 4 of 45 min left in this module

Module 9 · DatabasesLesson 4 of 4

Goal: Confirm you can say where lasting data belongs, pick a data model, and handle a connection string and its limits.

Five questions: four on this module, one on Module 7. Every answer explains itself, right or wrong.

Your app saves new signups to a signups.json file on its server. You add a second server behind the load balancer. What goes wrong?
You want to count requests per API key per minute, checked on every request. Which kind of database fits?
A teammate pastes DATABASE_URL into the README so everyone can run the app. What do you do first?
Your password is p@ss:word. Written into a connection string unencoded, the app can't connect. Why?
From Module 7: your app connects to the database with sslmode=require. What does that protect?

Retry as often as you like.

Before you go, name each part.

Databases at a glance: from memory

Name each part before you reveal it.

Keeps data safely outside your servers.
Tables, key-value pairs or documents.
Where the database is, and the password.
Reused connections, within the database's limit.
Where an app's lasting data lives, and how the app reaches it.