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?

we even have a starter for gql backend now: https://github.com/BigWhaleLabs/gql-backend-starter

can't remember exactly why we picked qgl over neo4j and i can be wrong on the exact reasoning

what we're always looking for is:
1. ease of development
2. type safety (typescript everywhere)
3. extensibility and availability of extensions

overall, we want to write less code — and i think that's why we didn' go with neo4j

Im built around neo4j for the prototypes, any reason you prefer gql over neo4j? (if familiar)