Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
_vvhw
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
91.
▲
by
_vvhw
4y ago
Sneakers and War Games (and also Tron) are great. We're running a consensus protocol bounty challenge for TigerBeetleDB inspired by them [1], with our distributed database simulator also being called The VOPR. [1] https://ww
92.
▲
Building SQLite with CGo for (almost) every OS
(zig.news)
3 points
by
_vvhw
4y ago
|
0 comments
93.
▲
How does your database recover from bit rot?
(twitter.com)
1 points
by
_vvhw
4y ago
|
0 comments
94.
▲
by
_vvhw
4y ago
This is a great list—to add two categories: If you need bloom filters, then use split block bloom filters [1] which use SIMD to increase speed from 30%-450%. If you need erasure coding, then use Cauchy Reed-Solomon instead of Reed-Solomon.
95.
▲
Consensus in Four Words
(twitter.com)
1 points
by
_vvhw
4y ago
|
1 comments
96.
▲
by
_vvhw
4y ago
> First of all, that's security, not safety. Lots of software exists in an environment where it isn't going to be attacked. I use the terms interchangeably on purpose, because safety and security are really two sides of the sam
97.
▲
by
_vvhw
4y ago
> I'm confused Thanks, I've tried to clarify that Zig provides spatial memory safety but not temporal memory safety, so hopefully it's less confusing. > "Simplicity" does not mean safety. Ceteris parabus, comp
98.
▲
by
_vvhw
4y ago
Between C++ and Rust, my bet would be that you decide Rust. But—also learn Zig in addition to Rust. Having seen first-hand how so many threat vectors these days are now supply chain attacks, having reported CVEs and earned P1 bounties in me
99.
▲
From Write-Ahead Log to LSM-Tree to LSM-Forest in 10 Minutes
(youtube.com)
1 points
by
_vvhw
4y ago
|
0 comments
100.
▲
by
_vvhw
4y ago
Surprisingly, some of the most powerful distributed systems algorithms or tools are actually deterministic. They're powerful because they can "load the dice" and so make the distributed system more intuitive for humans to rea
101.
▲
by
_vvhw
4y ago
> Allowing developers to think about a stream of operations that moves the databases from one legal state to another is super powerful. You're right—it's super powerful. We used this "RSM intuition" to test TigerBeetl
102.
▲
by
_vvhw
4y ago
Loved this! And here are a few more positive phrases: "total order", "committed/uncommitted log", "replicated state machine", "logical timestamp", "the network is not homogeneous", &quo
103.
▲
What Is a Database?
(scattered-thoughts.net)
2 points
by
_vvhw
4y ago
|
0 comments
104.
▲
by
_vvhw
4y ago
I had the recent privilege of interviewing Brian Oki [1] of Viewstamped Replication in September last year, since VSR is the consensus protocol that we use in TigerBeetle [2] to process a million financial transactions per second. One of th
105.
▲
Have you tried rubbing a database on it?
(hytradboi.com)
2 points
by
_vvhw
4y ago
|
0 comments
106.
▲
by
_vvhw
5y ago
And I understand that MongoDB are also testing with Antithesis [1] and getting lots of assurance from that, right? That gives me confidence. [1] https://github.com/mongodb/mongo/wiki/Testing-MongoDB-with-A...
107.
▲
by
_vvhw
5y ago
"I assume you've followed Jespen?" Yes! You might also want to check out autonomous deterministic testing, which is like Jepsen, but where you can explore many more state spaces by speeding up time, and where you can replay a
108.
▲
by
_vvhw
5y ago
"Gotcha. I'm also excited about the modern distributed databases. They're pretty awesome." Awesome! "HN comment is not the right place to design a resilient DB setup." Why not? In my experience, HN is always th
109.
▲
by
_vvhw
5y ago
"But I think you're imagining some kind of automatic link between the distributed nature of the blockchain leading to a distributed Postgres. But you would need to write out what your assumptions actually are before I could respon
110.
▲
by
_vvhw
5y ago
Single DB corruption and disk failures are more common than you think. "Single master, replicated to another region." Why do you recommend against using a modern distributed database? Is it that hard to spin up something like Cock
111.
▲
by
_vvhw
5y ago
"But are you arguing in favour of blockchain?" No, please see my original comment, where I made this clear: "I don't mean to advocate for cryptocurrency in any way." By "modern distributed database", I don
112.
▲
by
_vvhw
5y ago
"Why is this important?" Because without multi-region or multi-AZ durability, Wave could lose balances. For example, in the event of a DC fire. "Why can't they get by with a traditional main server plus some backups with
113.
▲
by
_vvhw
5y ago
"We need to keep track of our customers’ account balances. We need them to trust that their Wave balance is correct and Wave won’t lose the money." "At Wave, though, we prefer to use boring technology, and a simple relational
114.
▲
by
_vvhw
5y ago
Makes sense about not wanting to go boating. I've been deep into distributed consensus the past year—working on a 1 million TPS replicated state machine called TigerBeetle [1]. I would have enjoyed even more detail, only to understand
115.
▲
Etcd v3.5.[0-2] is not recommended for production
(groups.google.com)
1 points
by
_vvhw
5y ago
|
0 comments
116.
▲
by
_vvhw
5y ago
Are we allowed to share repos we've written? :) If so, then here's distributed consensus in Zig: https://github.com/coilhq/tigerbeetle/blob/main/src/vsr/repl... Something that differe
117.
▲
by
_vvhw
5y ago
> I like the author's solution (always use bounded queues) because it usually forces you to confront back-pressure up front. I work on a system that can process a million financial transactions a second, and this principle of "
118.
▲
Flexible Quorums for Better SuperBlock Resiliency
(twitter.com)
1 points
by
_vvhw
5y ago
|
0 comments
119.
▲
by
_vvhw
5y ago
Sure, C is a fine choice today. However, since the subject matter in this book can potentially have a half life of 10-20 years, perhaps a more modern C in the same performance space with easy compilation and quick learning curve might be be
120.
▲
by
_vvhw
5y ago
Can't wait to read a copy. The title is great. I knew exactly what this was about before I clicked through. I've also enjoyed your blog over the past few months, especially your post on the Eytzinger Layout [1], which we've i
More ›