vvern

8 ms·

31.
by vvern 2y ago
What I’m hungry for is not so much this coherent application for exploring json data but rather a set of React components to integrate explorations like this into a web app. Does anybody know of any good components or libraries for that?
32.
by vvern 2y ago
Transactional workloads over datasets in the single digit petabytes.
33.
by vvern 2y ago
Cockroach is also doing 3x replication of the data, so I don’t think that’s particularly relevant here. Cockroach serverless will dynamically scale up sql serving processes based on load. The storage and compute are separated in the cockroa
34.
by vvern 2y ago
Last time I checked, the cockroach serverless pricing model and free tier were cheaper than planet scale for small projects. IIRC, the dedicated cloud product was also cheaper if you kept it utilized. What’s your evidence that planetscale i
35.
by vvern 2y ago
Maybe one day the buck2 ecosystem will evolve to be that bazel replacement. It has a much smaller core. Right now it’s lacking in ecosystem support, tooling, examples, and a local build sandboxing (which could be fine if there was an easy t
36.
by vvern 2y ago
Can you provide some links to some projects? You’ve piqued my interest
37.
by vvern 2y ago
CockroachDB has a similar feature built in. It takes existing queries which are slow and then analyzes hypothetical indexes for better query plans and suggests them. You can add them in the console ui with one click. It’s pretty useful.
38.
by vvern 3y ago
Online schema changes (and upgrades) are absolutely critical for high-availability applications. In cockroachdb all schema changes are online and work more or less like this. One thing you give up with more or less all of these things is th
39.
by vvern 3y ago
I think crossing the chasm resonates more for a later stage, rather than just for getting started. I read it and felt like it really applied a lot more to my experience at a multi-hundred person company trying to become sustainable and publ
40.
by vvern 3y ago
Table driven tests are a lot better than a bunch of imperative tests but they rapidly become unwieldy to debug, maintain, and evolve. Their readability often isn’t great. If you’re using go, check out https://github.com/cock
41.
by vvern 3y ago
As hot of a take is that macros and meta programming are going to make startup and code bloat better
42.
by vvern 3y ago
Safety third
43.
by vvern 3y ago
Any good resources/deeper dives into the details of what actually happens on modern computers when making these syscalls on, say, linux? I might have a reasonable idea about what goes on when performing a mode switch or context switch,
44.
by vvern 3y ago
> yes I know it runs Linux binaries unmodified Is it that it runs Linux binaries unmodified or that it runs vms and manages VMs which run Linux, and as an end-user, that's what you run your software in?
45.
by vvern 3y ago
“Heat in the wilderness” must be so small in terms of global emissions footprint to be almost irrelevant, no? The wilderness implies ultra low density sort of by definition.
46.
by vvern 3y ago
Go has a mechanism to spawn a new thread (m in ho runtime parlance) if it thinks one of its threads might be blocked in a cgo (go’s “native function” equivalent). That prevents stuff like this.
47.
by vvern 3y ago
Is there a definition of “code forge” somewhere?
48.
by vvern 3y ago
A place that volatile shows up in C today that is stunningly handy is when writing eBPF programs. In eBPF you have to appease a verifier which is trying to prove safety and liveness properties of the compiled program. To prove safety proper
49.
by vvern 3y ago
I’ve found the datadriven[1] testing approach in go to be quite effective. The idea is that you leverage a standardized file structure to construct a little DSL for testing your code. This allows you to write expressive tests that print the
50.
by vvern 3y ago
I’d love to play with and explore this code. Please put a license on it. Code without a license should be assumed toxic and if you’re paranoid (like me) shouldn’t be read. This sort of thing feels like a good Apache or MIT fit.
51.
by vvern 4y ago
One approach could be to compile the core or file loader to WebAssembly, load the file using the WebAssembly which will ensure there’s nothing nefarious in terms of reaching outside the desired buffer, and then marshal the whole object acro
52.
by vvern 4y ago
I don't think it's fair to say it's a NoSQL database. It's very much a transactional, consistent SQL database.
53.
by vvern 4y ago
CockroachDB uses a skip list for its “timestamp cache” data structure, used to implement serializable isolation. The data structure records reads and exists to ensure that writes cannot rewrite history. This[1] library is the basis of the i
54.
by vvern 4y ago
Can we just properly price carbon emissions and be done with it?
55.
by vvern 4y ago
Can you say more about workloads which suck for either of the two databases at their default settings?
56.
by vvern 4y ago
dragonflycache sounds reasonable.
57.
by vvern 4y ago
> utilize transactions correctly This seems hard to do in Vitess or PlanetScale given the technically READ UNCOMMITTED isolation [1] when cross shard, and, in scaled deployments, will still require experimental 2PC [2] cross shard transa
58.
by vvern 4y ago
> They have to be on the same logical shard This is a pretty major limitation. Part of the reason to use Vitess is to scale out. It is often very valuable to have a small number of root elements in a star schema and to have foreign keys
59.
by vvern 4y ago
I’d love to see benchmarks.
60.
by vvern 4y ago
To clarify, FoundationDB has some documented multi-region features, but it's not at all clear that anybody who runs it at scale relies on those multi-region features [1]. Even if they do, it's not obvious they run this Fearless DR

More ›