interesting that it's more like mongo than neo
Post by twetch#6113
I would love if you could elaborate on that thought as I'm not familiar with either
What the chain says
- Block
- 660 013
- Time
- 2020-11-05T19:57:45Z
- Signer
- 12Cq4woAq2mTkusvPrY8CxyAdnueBFAcfh
- App
- twetch
- Type
- post
- Content type
- text/plain
- Name in tx
- twetch#6113
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
Signed by
12Cq4woAq2mTkusvPrY8CxyAdnueBFAcfh VerifiedReplies (15)
of course. there are a what we call SQL (relational) databases and NoSQL (non relational) databases. SQL is pretty set theoretic with joins, unions etc across tables, NoSQL is more open with four types:
- document store
- key value
- column store
- graph
mongo is a document store database, basically its a complex key value pair. mongo was created to store JSON objects over a decade ago during the rise of javascript. despite its popularity and ease of use, its a poor data storage mechanism at scale
twetch#864 6.0y
Scylla and cassandra like nosql would also be appropriate. I think the best is a combination of multiple different stacks, even transactional maybe on top. I wouldn’t recommend mongo it doesn’t scale. Xoken vega looks promising.
neo4j is a graph database. this is based off of graph theory and handles every object as nodes and edges. this was kind of pioneered by the sparql movement awhile back, but wikidata uses graph databases as their backend for many things.
though neo is quite interesting, i personally have never seen it scale it while outperforming relational databases. there is decades of knowledge for how to scale relational databases, the same can't be said for non relational (excluding columnstore/kvp)
twetch#7453 6.6y
a graph db is merely abstraction