Intro: We need to talk about your "Modern Stack"
Let’s be real for a second. We’ve all been there: You have a "simple" project idea. Two hours later, you’re staring at a Docker Compose file with PostgreSQL, Redis for caching, Neo4j because "graphs are cool," and a Node.js backend just to move JSON from A to B.
Why are we doing this to ourselves?
I’m a medior dev. I’ve reached the point in my career where I’m too tired to write the same CRUD boilerplate for the 100th time. I just want to build things that work. And that’s when I stumbled upon SurrealDB.
What is SurrealDB? (Besides a cool name)
Imagine if SQL, MongoDB, and GraphQL had a baby, and then that baby was raised by Firebase but grew up to be actually flexible.
SurrealDB is a multi-model database. It doesn't care if you want documents, relational tables, or complex graph structures. It just says: "Sure, why not both?"
Why you (as a lazy dev) should care:
The "Backend Killer" (No, seriously): SurrealDB has built-in Row-Level Security (RLS) and authentication. You can connect your frontend (React, Vue, whatever) directly to the database. No more writing 500 lines of Express.js just to check if user_id === owner_id.
Schema-Flexible (The "I'll decide later" feature):
You can start schema-less (just dump data) and then enforce a schema once you actually know what you're building. It's perfect for prototyping without the "oops, I forgot a migration" headache.
Graph Relations without the PhD:
Remember trying to write a recursive CTE in SQL to find "friends of friends"? In SurrealDB, it's literally just an arrow: SELECT ->knows->person FROM user:me. My brain thanked me.
A Quick Reality Check
Is it magic? Almost. Is it perfect? Well, it's still evolving. But if you're building a startup or a side project and you're a "team of one," using a traditional stack is like bringing a tank to a knife fight. It’s overkill and you’ll probably hurt yourself.
What’s next?
In the next part of this mini-series, I’m going to show you how I deleted 70% of my backend code using SurrealDB’s auth layer.
Spoiler: It felt amazing.
