Why should I stop thinking about a graph database for…like everything

cto @ bwl.gg (lunchbreak.com), 80M+ users (bdut.ch) 🙏 built @remindme, @mintit, @gpt, @healthbot, farcantasy.xyz

@backpack put a bank in your pocket and use your money whenever, wherever, however without permission

/backpack
/notdevin
icebreaker.xyz/notdevin

@warpcastadmin.eth you ever use a graph db like neo4j or the like? 

I started using one for a specific agent application and I can’t stop seeing things I want to put in the graph instead of using a PG or a bucket. There are relationships I want to create which is why I didn’t want to use a blob store but the data doesn’t necessarily need to be causing migrations so PG seems unnecessary, but now I’m seeing graphs everywhere and need a sanity check. 

Thoughts?

i use gql daily with psql and/or mongo under the hood

prisma and a bunch of extensions allow writing code and everything like docs, sandbox, schemas, etc generate automatically, e.g. see backend.lunchbreak.com, we write code — everything else generates automatically

also allowing frontend fetch only what it needs to fetch without creating multiple endpoints

and type safety out of the box

as for graphs? couldn't care less what happens under the hood

it works and it's fast