2
0 Comments

Don't design your database like a frontend developer

The #1 problem I faced when setting up a database for a product was fragile data. As a frontend developer this usually happened because I created my db schema based on what I was trying to render.

When was the last time that the first UI you built was the same 3-6 months later? lol I just didn't know any better.

Here is one thing you should think about when creating your database schema that will hopefully help you make better data decisions upfront: Will this cause data repetition? Both in the database and in the app requiring extra processing that will slow down your rendering.

Here is a real world example to see this in action and is what I wish I had read when I was trying to design a database for the first time:

Real World Example

Who else has been bit by bad database schema?
  1. Me
  2. Liar
Vote
Trending on Indie Hackers
I've built a 2300$ a month SaaS out of a simple problem. 19 comments I'm building the MCU of SaaS 💎 12 comments 🔥 Roast My Landing Page 11 comments Where can I buy newsletter ad promos? 8 comments Key takeaways growing MRR from $6.5k to $20k for my design studio 6 comments YouTube? How to start 5 comments