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
Reaching $100k MRR Organically in 12 months 29 comments Passed $7k 💵 in a month with my boring directory of job boards 15 comments 87.7% of entrepreneurs struggle with at least one mental health issue 14 comments How to Secure #1 on Product Hunt: DO’s and DON'Ts / Experience from PitchBob – AI Pitch Deck Generator & Founders Co-Pilot 11 comments Competing with a substitute? 📌 Here are 4 ad examples you can use [from TOP to BOTTOM of funnel] 10 comments Are you wondering how to gain subscribers to a founder's X account from scratch? 8 comments