Post by twetch#6113

12Cq4w…Acfh Key · twetch

#Urbit :: https://youtu.be/E4DFuAZQ32Y : Logan Allen discusses the new graph-store.

What the chain says
Block
660 010
Time
2020-11-05T19:03:16Z
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 Verified

Replies (13)

1F8LZF…8gsQ Key · twetch
Replying to@12Cq4w…Acfh

interesting that it's more like mongo than neo

12Cq4w…Acfh Key · twetch
Replying to@1F8LZF…8gsQ

I would love if you could elaborate on that thought as I'm not familiar with either

1F8LZF…8gsQ Key · twetch
Replying to@12Cq4w…Acfh

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
1F8LZF…8gsQ Key · twetch
Replying to@1F8LZF…8gsQ

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.

Continue thread →

This thread is longer than one page shows. Open a reply to see what follows it.