If you are vibe coding and wanna know you’re going to have a hard time with this one, Just look at the database schema

If it is something very complicated and a lot of interdependencies then my brother you are cooked

Those interdependencies mean databases demanding a lot of things

And if your back end is not able to keep up with that there are going to be errors

And even if your back end is able to keep up with that if your front end is not able to communicate with your back end properly

Then your backend might not be able to get all that executued properly then again you are fucked

That’s why I’m an advocate of building client side self isolated applications which communicate with other parts in single json blob so that the point of failure is just one

Build the entire operation in memory, validate it, then send

This will keep your database simple and keep the expectations from your communication in app managable

When vibe coding, always minimize coordination points

---

Complex DB Schema
↓
Backend struggles with interdependencies
↓
Frontend can’t coordinate multi-step operations
↓
Partial updates, inconsistent state, chaos

---