RefineDB
Data
document database
SHOW HN2021
113points
26comments
#472of 2,533 in 2021
Top 19%of 2021 by points
How HN took it
CuriousMostly questions and neutral comments
3 positive, 8 neutral or asking, 0 mixed, 0 critical, out of 11 comments about the project. Thread score +0.24.
Idea: 3 for, 0 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Interesting, promising concept for a typed document store
From 3 comments
This looks really promising! Could you provide at a high-level what this aims to offer over FoundationDB's RecordLayer[1]? [1] https://github.com/FoundationDB/fdb-record-layer
monstrado on HNGreat work! The ideas are intriguing. I want to know more about the quering approach. How is it better than SQL or other document quering representations? What is a concurrent…
lewisjoe on HNLooks very very interesting. Nice work. Plans to support more DBs? do you intend for the OS community to build the translation layers?
danr4 on HN
Key-value store as a primitive is powerful
From 1 comment
I love this - a KV store is such a powerful primitive, I've wondered why we don't see more projects like this
rmorey on HN
Objections
Nested documents are hard to query compared with SQL
From 1 comment
>> SQL is a nice language for querying relational data, but RefineDB deals with nested documents. Can't you just expand the nested documents into a non-nested version and use…
StreamBright on HN
Requests
Support more key-value backends such as TiKV and RocksDB
From 2 comments
Looks very very interesting. Nice work. Plans to support more DBs? do you intend for the OS community to build the translation layers?
danr4 on HN> can you explain what the issue is with it? And do what are ways to resolve it if TiKV does not resolve it themselves? TiKV is based on multi-raft + Percolator where there is no…
losfair on HN
Realtime data-changed event streams
From 1 comment
This is great! Can you implement a data-changed event stream like the RethinkDB changefeed and Firebase triggers? https://rethinkdb.com/docs/changefeeds/javascript/…
zackmorris on HN
SQL to RefineASM transpiler
From 2 comments
This is great! Can you implement a data-changed event stream like the RethinkDB changefeed and Firebase triggers? https://rethinkdb.com/docs/changefeeds/javascript/…
zackmorris on HNIf a document DB is strongly typed, if should be possible to implement SQL to return results right?
smoyer on HN
Questions
How does it compare with FoundationDB's Record Layer
From 2 comments
This looks really promising! Could you provide at a high-level what this aims to offer over FoundationDB's RecordLayer[1]? [1] https://github.com/FoundationDB/fdb-record-layer
monstrado on HN- Both FDB record layer and RefineDB support complex types and indexes (with the details differing a lot); FDB record layer's index support is more complete for now. - FDB record…
losfair on HN
How does the query language differ from SQL
From 3 comments
Great work! The ideas are intriguing. I want to know more about the quering approach. How is it better than SQL or other document quering representations? What is a concurrent…
lewisjoe on HNThanks for the questions! > How is it better than SQL or other document querying representations? SQL is a nice language for querying relational data, but RefineDB deals with…
losfair on HN> RefineDB has types, and I’m not aware of any other query language that deal with types (let me know if I'm wrong). In what sense is SQL not typed?
e12e on HN
Plans for non-primary indexing
From 2 comments
This looks really cool! Perhaps you should show some nontrivial examples of (read) queries in RefineASM. Also, what are your plans (if any) for non primary indexing? Storage…
voidmain on HNOn non-primary indexing: It's a nice thing to have but I haven't decided on the design yet. My current preference is to implement the non-primary index feature as a library once…
losfair on HN
Alternatives named
FoundationDB Record Layer
From 1 comment
This looks really promising! Could you provide at a high-level what this aims to offer over FoundationDB's RecordLayer[1]? [1] https://github.com/FoundationDB/fdb-record-layer
monstrado on HN
TerminusDB
From 1 comment
TerminusDB's WOQL deals with types. As with RefineDB, TDB is designed to work with nested documents.
LukeEF on HN
EdgeDB
From 1 comment
>other query language that deal with types EdgeDB has a similar strongly typed schema [1], see their edgeQL/graphQL ability. Their typed schema also facilitates computed…
unraveller on HN