4 ms·
If you only need a few graph queries then you could just use SQLite, it’s capable of doing it (I have done it before). But writing graph queries in SQL is painf
by chillfox 4y ago
If you only need a few graph queries then you could just use SQLite, it’s capable of doing it (I have done it before). But writing graph queries in SQL is painful, so I wouldn’t do it if you need more than a handful.
- mcv 4y agoExactly. There's no need for a graph database if you're not going to be searching for complex relationships. And once you do, SQL is hell. I don't know of any SQLite-like graph database. I'm still a fan of neo4j.
- olavgg 4y agoI also really like Neo4J, but the community version is very crippled. Still though, I've worked around it and do hot backups with ZFS and run multiple database processes to support multiple customers.
- alfiedotwtf 4y agoYeah, Neo4J is neat but I don't want to stand up services... that's why I wondered if there were some that linked in easily