Choosing a Database by Prompt
Let AI recommend storage.
Choosing a Database by Prompt is a free Vibe Coding lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Vibe Coding learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Not All Databases Are the Same
There are many kinds of databases, and they are good at different jobs. The two big families you'll meet most are relational (like PostgreSQL or SQLite) and document (like MongoDB).
When vibe coding, you don't have to memorize them all. You describe your needs and let the AI recommend.
Relational in One Sentence
A relational database stores data in tables with rows and columns, like a spreadsheet, and lets tables link to each other.
It shines when your data is structured and connected, for example users who each own many orders.
Explain in plain language when a relational database is a better fit than a document database for a typical web app.Document in One Sentence
A document database stores data as flexible JSON-like documents instead of strict tables.
It is handy when each record can have a different shape, or when you are still figuring out your structure. The trade-off is weaker guarantees about how data connects.
Describe, Don't Dictate
Instead of guessing the right tool, describe your app and ask for a recommendation. Good prompts include what you store, the rough scale, and your priorities.
The AI can match those needs to a database far faster than browsing comparison articles.
I'm building a booking app for a small gym: members, classes, and reservations.
Recommend a database and explain why it fits. Mention one alternative and its downside.Start Simple With SQLite
For many new projects, SQLite is a great first choice. It is a relational database that lives in a single file, needs no server, and is easy to set up.
You can always move to a bigger database later, and a good AI prompt can ask for an easy upgrade path.
Set up SQLite for my project as the starting database.
Keep it simple, and note what I'd need to change later to move to PostgreSQL.Managed vs. Self-Hosted
You can run a database yourself, or use a managed service like Supabase or PlanetScale that hosts it for you.
Managed services save setup time and handle backups, which is great for solo vibe coders. Mention your preference so the AI tailors its setup steps.
Matching the Stack
Your database choice should play nicely with the rest of your stack. A Next.js app, a Python script, and a mobile app each have smooth and rough options.
Tell the AI your framework so it recommends a database with good support and clear setup instructions.
My app is built with Next.js and deployed on Vercel.
What database options integrate most smoothly with this stack, and which would you pick for a beginner?Ask About Costs
Some databases are free at small scale, then charge as you grow. A surprise bill is no fun.
Ask the AI about pricing tiers and free limits before committing, so your choice fits both your project and your budget.
Compare the free tiers of Supabase, PlanetScale, and a self-hosted PostgreSQL.
For a hobby project with light traffic, which keeps costs near zero?Beware One-Word Answers
If you ask "which database is best?" you'll get a generic answer. Best depends on your situation.
The more context you give, the sharper the recommendation. Treat the AI like a consultant who needs the full brief, not a magic oracle.
Locking In the Decision
Once you've chosen, ask the AI to record the decision and reasoning in your project, often in a README or a notes file.
This keeps future you (and future prompts) consistent, so you don't accidentally drift to a different database mid-build.
We decided to use SQLite for now.
Write a short note in the README explaining this choice and when we'd switch to PostgreSQL.Reversible Choices
Good news: early database choices are rarely permanent. If you keep your data access in one place, swapping databases later is far easier.
You can even ask the AI to structure your code so the database is easy to replace down the road.
Quick Check
Test your understanding of choosing a database by prompt.
Recap
You met relational and document databases and learned to choose by describing your app, not by dictating a tool. SQLite is a friendly starting point, and managed services save setup work.
Always share stack, scale, and budget in your prompt, and record the decision. Next, you'll model your tables with AI.
Frequently asked questions
Is the “Choosing a Database by Prompt” lesson free?
Yes — the full text of “Choosing a Database by Prompt” is free to read here on the web, and the Vibe Coding course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Vibe Coding course, upgrade to CoddyKit PRO.
What will I learn in “Choosing a Database by Prompt”?
Let AI recommend storage. You practise Vibe Coding with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Vibe Coding?
No prior experience is required. Vibe Coding on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Choosing a Database by Prompt” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Vibe Coding lesson?
Yes. Every Vibe Coding lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Why Apps Need Data
- Choosing a Database by Prompt
- Modeling Tables with AI
- Saving and Reading Records