refset

16 ms·

61.
by refset 2y ago
> a log entry must be appended that says the log is closed Related concepts: 'epoch' (distributed consensus), 'watermark' (out-of-order stream processing)
62.
by refset 2y ago
Explicit query plan pinning helps a lot, alongside strong profiling and monitoring tools.
63.
by refset 2y ago
> just unrolling several unnecessary nested subqueries, and adding a more selective predicate And state of the art query optimizers can even do all this automatically!
64.
by refset 2y ago
I wonder where things will stand in 10 years from now. Will many orgs still be consuming vanilla Postgres, or will most workloads have shifted to ~proprietary implementations behind cloud services like "Aurora PostgreSQL Limitless Data
65.
Principles for a Diverging Desktop Future (2020)(divergent-desktop.org)
2 points by refset 2y ago|0 comments
66.
by refset 2y ago
For anyone happy enough to consider dealing with the JVM instead of C, and Clojure instead of SQL, I think this CINQ project can deliver on much of what you're looking for here: https://github.com/wotbrew/cinq &gt
67.
by refset 2y ago
If you would like some exposure therapy: https://databasearchitects.blogspot.com/2024/12/advent-of-co... [0] [0] Recent discussion https://news.ycombinator.com/item?id=42577736
68.
TodoMVC – Electric v3(electric.hyperfiddle.net)
3 points by refset 2y ago|0 comments
69.
by refset 2y ago
More specifically, DBOS Inc. raised a $8.5 million seed round [0] and is backed by Michael Stonebraker (the creator of Postgres). I initially assumed Andy was alluding to this when he wrote "the most famous database octogenarian splash
70.
by refset 2y ago
Interesting! MVCC mechanics aside, it's also worth remembering that work_mem is only 4MB by default [0], so large intermediate results will likely spill to disk (e.g. external sorts for ORDER BY operations). [0] https://www.
71.
The missing SQL sub-queries(xtdb.com)
2 points by refset 2y ago|0 comments
72.
by refset 2y ago
An EAV table is usually a symptom of a wider set of issues with schema management, and in contrast, most people I've spoken to who have implemented their own EAV tables on top of a regular SQL database have ended up regretting it becau
73.
by refset 2y ago
Writing Clojure without spaghetti isn't too hard, and definitely more practical than waiting for a Jepsen alternative to come along. The Jepsen author gave a great talk on all the performance engineering work that has gone into it, Jep
74.
by refset 2y ago
I meant 'scale' mostly in the sense of 'complexity' (sorry!). If you only have a small number of tables you need/want this versioning for then the DIY approach is workable, but if you want to apply this across an en
75.
by refset 2y ago
How do you find it when you scale it up to every table, every query?
76.
by refset 2y ago
The upcoming XTDB v2 is a SQL-first engine. We also built an experimental Clojure/Datalog-like 'XTQL' language to go along with it, to provide some continuity for v1 users, but the primary API is now SQL over the Postgres w
77.
by refset 2y ago
Agreed, but it seems likely that people will casually pick this up instead of actual Postgres without fully appreciating the potential for consistency issues. I'd feel happier if AWS marketing applied your description of the value prop
78.
by refset 2y ago
> Aurora DSQL isolation level is equivalent to PostgreSQL Repeatable Read. So it lacks Serializable isolation also, but I guess that's the secret to how it "offers the fastest distributed SQL reads and writes".
79.
Advent of SQL(adventofsql.com)
5 points by refset 2y ago|0 comments
80.
by refset 2y ago
It doesn't help that SQL's recursive CTE model is a bit odd - Frank McSherry proposed a much nicer alternative (which Materialize has implemented): https://materialize.com/blog/recursion-in-materialize/
81.
Planning for Momentum (2021)(increment.com)
1 points by refset 2y ago|0 comments
82.
BoxLang(boxlang.io)
2 points by refset 2y ago|1 comments
83.
by refset 2y ago
> The Kafka transaction protocol is fundamentally broken and must be revised. Ouch. Great investigation work and write-up, as ever!
84.
by refset 2y ago
Interesting, thanks for digging that answer out. HN is a treasure trove!
85.
by refset 2y ago
Agreed, I would love to see a large scale implementation and experience report. I also wonder about combining the Bthreads model with the notion of 'durable execution', as demonstrated by the folks at DBOS: https://www.
86.
by refset 2y ago
Context from the previous post in the series: > Behavioral Programming is a relatively new programming paradigm that excels at isolating and composing behaviors in event driven system. > Behavioral programming was invented by David
87.
Bthreads: A Simple and Easy Paradigm for Clojure(thomascothran.tech)
85 points by refset 2y ago|9 comments
88.
by refset 2y ago
Like a many-to-many join table?
89.
by refset 2y ago
DBOS [0] is outwardly similar although it's much younger. IIUC, internally DBOS is able to be more efficient and support lower latencies than Temporal because of the way it can push work down into Postgres stored procedures. [0] https
90.
by refset 2y ago
** Clojure is _a_ language [...] (apologies!)

More ›