refset

21 ms·

361.
by refset 3y ago
XTDB is a deterministic, single-writer system that leans on existing tech to handle all the hard distributed & durability aspects (e.g. piggy-backing on Kafka for ACID + HA), so Jepsen would have relatively limited applicability but it
362.
by refset 3y ago
Datomic's "immutable database + Datalog" was definitely the biggest source of inspiration but XTDB has a lot of differences - I wrote this FAQ entry up a few years back: https://docs.xtdb.com/resources/fa
363.
by refset 3y ago
XTDB 2 will compute and maintain incremental indexes on-the-fly based on the raw data, so index updates will present far less operational impact. This also means the transaction log is now ~ephemeral in the new architecture (no more event-s
364.
by refset 3y ago
True! Life finds a way. I wonder whether real-life athletes etc. benefit from a more realistic dream legs simulation experience.
365.
by refset 3y ago
Omnigres, "Postgres as a platform", is very much in the same vein: https://github.com/omnigres/omnigres
366.
by refset 3y ago
I can relate heavily. The recurring ability to hover by kicking my legs around is profoundly liberating and a deeply familiar sensation at this point. Dreams feel like living a parallel life :)
367.
by refset 3y ago
Interesting read! I would like to add: * databases need to get better yet at schema management and workload isolation to enable multiple applications to properly integrate through the database (as traditionally envisioned) * HTAP seems inev
368.
by refset 4y ago
Thanks for sharing the summary. There's also this Strange Loop 2017 talk "Datafun: a functional query language" with an early overview of this research: https://www.youtube.com/watch?v=gC295d3V9gE
369.
by refset 4y ago
To be clear I'm not experienced enough to judge all these tradeoffs properly either, and I've never worked with Datomic. I suppose my main point is that an ideal database UX would avoid having to write processing/transformati
370.
by refset 4y ago
I'm not the OP, but thinking well beyond the original topic of in-memory reactive programming (where my answer would be quite different) to the world of long-lived durable databases... one perspective to consider is that any system bui
371.
How to beat social media's network effects(tfos.co)
1 points by refset 4y ago|0 comments
372.
by refset 4y ago
> practically it's simply tough to draw the line between assuring that historical data is still handled and rendered correctly and getting rid of overhead and complexity of a growing and evolving application Agreed, the issue of mai
373.
by refset 4y ago
Agreed, my understanding is that Datalog has a distinct (though related) lineage that directly emerged from Prolog (i.e. logic programming, not relational algebra / database theory) - skimming the introduction of "Horn Clauses and
374.
by refset 4y ago
> Datalog implementations can use different (or multiple, switchable) strategies Including distributed strategies, as seen in Bloom http://boom.cs.berkeley.edu/
375.
by refset 4y ago
The topic of dealing with history in databases seems to go most of the way back to the beginning of the field. I'm still hoping a copy of "Bubenko (1977) The Temporal Dimension in Information Modelling" turns up on the web ev
376.
by refset 4y ago
Hmm, it seems there's some SVG rendering issue when viewing directly. It should say "LMDB" in that empty spot. It renders okay for me on the GitHub readme: https://github.com/xtdb/xtdb (and here https:&
377.
by refset 4y ago
> Datalog has great compositionality, which is one of SQL's big weaknesses There's a good write-up on this aspect (amongst others) here: https://www.scattered-thoughts.net/writing/against-sql/ > re
378.
by refset 4y ago
Thanks for the insights and clarifications - I agree with all that completely :) I mainly responded because "Datomic ∈ Datalog" is worthy of discussion in itself ...but I now realise this is probably the wrong subthread for that.
379.
by refset 4y ago
Flix definitely looks interesting! For comparison, I ported the "Datalog Enriched with Lattice Semantics" example from that homepage to XTDB's (Clojure) Datalog after I saw it posted on HN originally: https://gist.
380.
by refset 4y ago
It's true that this SPARQL-inspired view of Datalog as a triplestore query language is quite a narrow interpretation compared to something closer to the academic Prolog roots like https://souffle-lang.github.io/ - what
381.
by refset 4y ago
XTDB, which is mentioned in the post, is subtly different from the other Clojure-based Datalog systems in this respect, because its Datalog engine executes in terms of multi-way joins using a "Worst-Case Optimal Join" implementati
382.
by refset 4y ago
Just noting that Crux has been rebranded to https://xtdb.com/ (as per https://xtdb.com/blog/crux-to-xtdb-rename/ )
383.
Emotional Management (2021)(scattered-thoughts.net)
1 points by refset 4y ago|0 comments
384.
by refset 4y ago
> I'd really love to see some research into deriving CRDT merge semantics from a formal description of application behaviour. I'm no expert, but I believe synthesis approaches are a strong step in that direction: https:/&
385.
by refset 4y ago
Well, at least we're getting through them eventually :)
386.
by refset 4y ago
Various aspects of query optimization like join planning and predicate selectivity estimation, e.g. as discussed in https://arxiv.org/abs/2010.00728
387.
by refset 4y ago
> Winternitz signatures are fascinating because they're secure while still being within the reach of most programmers and--as the article points out--they're quantum safe. Absolutely agreed, Winternitz is very approachable! At
388.
by refset 4y ago
Thank you! I guess the trick with this suggestion is to move the vertical line to directly beneath the text such that it doesn't need to be taller...which is probably a good enough workaround, even if not exactly what I was hoping for
389.
by refset 4y ago
Very neat! Any ideas how to add correct vertical line heights with multi-line / variable-height items? e.g. the vertical line next to "Jupiter" here is too short https://gist.github.com/refset/c6f3ac05cac
390.
by refset 4y ago
> I think some illustrations to accompany your ideas might go a long way as well I'm not the OP, but I built this visual tool recently which might be of interest https://bitemporal-visualizer.github.io/

More ›