4 ms·
We're in the middle of upgrading our docs/resources, maybe this is helpful? http://gun.js.org/docs http://gun.js.org/docs (note: some pages are broken) We have
by marknadal 9y ago
We're in the middle of upgrading our docs/resources, maybe this is helpful? http://gun.js.org/docs http://gun.js.org/docs (note: some pages are broken)
We have pretty in depth conversations on the chat room too, here https://gitter.im/amark/gun https://gitter.im/amark/gun but I'm more than willing to answer any other questions you have that might not be covered!
- bryanrasmussen 9y agowell basically I would just know where it falls short of Neo4J's capabilities, and if it is possible to have more than one graph running at the same time.
- marknadal 9y ago@bryanrasmussen , ah yes: - You can have more than 1 graph at the same time, yes. - Storing data on edges can be done in GUN by having an "edge node", Neo4j has a special built-in edge node which makes things easier (including bidirectional edges, which can be done in GUN, but requires making an edge node). - Neo4j's Cypher query language has a lot of built in edge search algorithms, we have not (but plan to) built these yet. - Neo4j has a very nice dashboard, our community has built a couple similar tools, but nothing as comprehensive. Summary: Neo4j, being over a decade old, has a lot of features that we haven't built yet. Why use GUN instead? The biggest kicker is it being based on a P2P/decentralized (Master-Master) architecture, which makes ops/scaling much easier and a ton of other things. If you don't need this, probably stick with Neo4j for its feature set.