Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
andreimatei1
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
Side-Eye – a production debugger for Go
(side-eye.io)
8 points
by
andreimatei1
2y ago
|
0 comments
2.
▲
by
andreimatei1
2y ago
Side-Eye is massively inspired by DTrace in some of its raw capabilities and the basic idea of dynamic instrumentation. Beyond that, they're very different. At a low level, DTrace is primarily geared towards debugging the kernel, where
3.
▲
by
andreimatei1
2y ago
Print debugging is the tool most people reach for when they can, but its biggest problem is that you have to change the source code to add the printfs. This is impractical in many circumstances; it generally only works on your local machine
4.
▲
by
andreimatei1
3y ago
This answer should go to the top.
5.
▲
by
andreimatei1
4y ago
Very nice work! It seems that Delve is used for inspiration and development, but Golang code is always compiled with frame pointers, I think. Is that right?
6.
▲
Back from the Future: Global Tables in CockroachDB
(cockroachlabs.com)
94 points
by
andreimatei1
4y ago
|
12 comments
7.
▲
by
andreimatei1
4y ago
Global Tables let database clients in any region read strongly consistent data with region-local latencies. They’re an important piece of the multi-region puzzle — providing latency characteristics that are well suited for read-mostly, non-
8.
▲
by
andreimatei1
5y ago
Cockroach lets you hash-shard your keys n-ways if you choose to through a feature called hash-sharded indexes ( https://www.cockroachlabs.com/docs/stable/hash-sharded-index... ) That's a trade-off: costlier ran
9.
▲
An Epic Read on Follower Reads in CockroachDB
(cockroachlabs.com)
26 points
by
andreimatei1
5y ago
|
0 comments
10.
▲
Early Patches Bring BPF to the Linux Scheduler
(phoronix.com)
4 points
by
andreimatei1
5y ago
|
2 comments
11.
▲
by
andreimatei1
5y ago
> its lack of ACID guarantees Our transactions implementation is our crown jewel. You might want to check your sources.
12.
▲
Don't Get Stuck in the Con Game (V3)
(pathelland.substack.com)
2 points
by
andreimatei1
5y ago
|
0 comments
13.
▲
by
andreimatei1
6y ago
I think the "default" will evolve with whatever offers the best "serverless" experience in the public clouds. In particular, the cheapest and most granularly-billed option.
14.
▲
by
andreimatei1
6y ago
> I agree that right now it doesn't make sense. This CRDB engineer respectfully disagrees. This thread takes it as a given that a non-distributed DB is better if you don't need to scale up (i.e. if you run a single "node&q
15.
▲
by
andreimatei1
7y ago
Working on it.
16.
▲
by
andreimatei1
7y ago
Would you mind providing a link to the empty arrays patch? Is this something CRDB should fix?
17.
▲
by
andreimatei1
7y ago
At GitHub they should be using CockroachDB (:P), a scalable relational database that also supports schema changes. Then their FKs would work just fine (albeit with some performance implications).
18.
▲
by
andreimatei1
8y ago
Perhaps I could emphasize things differently. FWIW, besides the fact that having a foreign key constraint in that schema would prevent the badness from happening, the even bigger reason why scenarios like that are unlikely is that, realisti
19.
▲
by
andreimatei1
8y ago
> The suggestion that this anomaly can occur in FaunaDB is wrong: You're right. I've removed the reference to FaunaDB. Sorry about that. What I've meant to reference is the snapshot isolation of FaunaDB's read-only tr
20.
▲
by
andreimatei1
8y ago
Hi Gab_CV, this is really cool! Congrats! Are you planning on writing any notes about what the port took? You commits are quite clean, but still some narrative would be really interesting.
21.
▲
by
andreimatei1
8y ago
We have clients using CRDB in pretty constrained environments, and they use it primarily because of the easy administration. I think you'll find it easier to use than a MySQL or Postgres, for example.
22.
▲
by
andreimatei1
8y ago
https://github.com/tbg/bikesheddb
23.
▲
by
andreimatei1
9y ago
> Postgres supports different modes of replication, including synchronous replication to avoid losing any data on node failure. I would like to understand this better, for my edification. The best source on the exact semantics of pg repl
24.
▲
by
andreimatei1
9y ago
Ozgun has done a good job describing some of Citus' benefits; allow me to write the CockroachDB-biased answer. Btw, congrats to all the Citus people on your launch. The highest-level architectural difference is, in my opinion, the fact
25.
▲
by
andreimatei1
9y ago
I believe this suggestion came up at the time. I think we didn't do anything like it because it would have been more complicated both to implement and to describe, and because it's not particularly common for people to use/ne
26.
▲
by
andreimatei1
9y ago
Why do you say that they don't hold, exactly? We take our consistency guarantees, and correctness more generally, deadly serious. I think it's fair to say that we did quite well on Aphyr's review; he's found some quite o
27.
▲
by
andreimatei1
9y ago
I can all but promise you that no CRDB dev will tell you to go F* yourself :P
28.
▲
by
andreimatei1
9y ago
I'm not sure how interleaved tables help you with multi-tenancy, but I'd be curious to find out. If, by multi-tenancy, you mean sharing a CRDB cluster between different applications or different instances of the same application,
29.
▲
by
andreimatei1
9y ago
FWIW, CRDB should be a good fit for people worried about database lock-in. You'd only be "locked in" if you discover that we're much better than the alternatives :) CRDB uses the standard SQL language. Also, CRDB speaks
30.
▲
by
andreimatei1
9y ago
Besides the blog, you can find interesting stuff in the source repo, in the technotes and RFC dirs: https://github.com/cockroachdb/cockroach/tree/master/docs/te... https://github.com/
More ›