HackerTrans
TopNewTrendsCommentsPastAskShowJobs

riccomini

no profile record

Submissions

Distributed Compaction in SlateDb

ryandielhenn.github.io
2 points·by riccomini·قبل 30 يومًا·0 comments

[untitled]

1 points·by riccomini·قبل شهرين·0 comments

[untitled]

1 points·by riccomini·قبل 3 أشهر·0 comments

[untitled]

1 points·by riccomini·قبل 3 أشهر·0 comments

[untitled]

1 points·by riccomini·قبل 3 أشهر·0 comments

[untitled]

1 points·by riccomini·قبل 3 أشهر·0 comments

[untitled]

1 points·by riccomini·قبل 3 أشهر·0 comments

[untitled]

1 points·by riccomini·قبل 3 أشهر·0 comments

Something Is Happening

rng.md
3 points·by riccomini·قبل 3 أشهر·0 comments

MCP Server Could Have Been a JSON File

materializedview.io
4 points·by riccomini·قبل 10 أشهر·1 comments

Show HN: ZeroFS: The S3FS that does not suck

github.com
10 points·by riccomini·السنة الماضية·0 comments

Kafka: The End of the Beginning

materializedview.io
2 points·by riccomini·السنة الماضية·0 comments

Everything You Need to Know About Incremental View Maintenance

materializedview.io
9 points·by riccomini·السنة الماضية·6 comments

The Bond Market at the 5% Threshold

dataandpolitics.net
19 points·by riccomini·السنة الماضية·1 comments

[untitled]

1 points·by riccomini·السنة الماضية·0 comments

AI IDEs Need Moats

materializedview.io
2 points·by riccomini·السنة الماضية·0 comments

Comparing Apache, CNCF, and Commonhaus

cnr.sh
2 points·by riccomini·السنة الماضية·0 comments

Show HN: A static site generator toolkit written in Python

github.com
2 points·by riccomini·السنة الماضية·0 comments

S3 Is the New SFTP

materializedview.io
1 points·by riccomini·قبل سنتين·0 comments

Slatedb/Clean_slate.md

github.com
1 points·by riccomini·قبل سنتين·0 comments

comments

riccomini
·السنة الماضية·discuss
DD supports lattices that allow it to compute at multiple points in time simultaneously. As I understand it, DBSP limits time to one diff at a time. Lalith can correct me if I’m off base on this. :)
riccomini
·قبل سنتين·discuss
Great question! We started out with the design you described--WAL as L0. But we found that there's a bit of a tension between wanting to have L0 SSTs be larger (and having fewer of them) to reduce metadata size, while we wanted to keep WAL SSTs small and frequent (to reduce async/await latency).

Basically, we wanted to have WAL writes go on the order of milliseconds, but we wanted L0 SSTs to be larger since they actually service reads.

The architecture page has more detail if you haven't found it yet:

https://slatedb.io/docs/architecture