tschottdorf

5 ms·

1.
How I Journal, 1000 Days In(tbgatwork.substack.com)
2 points by tschottdorf 2y ago|0 comments
2.
by tschottdorf 5y ago
I'm close to a 35+ yo engineer and have been with my current employer for over six years, mostly based in Europe. There are multiple ICs, myself included, in positions like the ones you seem to be looking for, and we are hiring. I know
3.
by tschottdorf 5y ago
I tried to use this but once I start entering tasks I don't see how to proceed. There's no way forward from neither there nor the project list page. Am I missing something?
4.
by tschottdorf 6y ago
There is an extension to linearizability that takes General Relativity into account. Paywalled unfortunately: https://link.springer.com/chapter/10.1007/978-3-662-45174-8_... I agree that whatever can be done in an
5.
Availability and Region Failure: Joint Consensus in CockroachDB(cockroachlabs.com)
15 points by tschottdorf 7y ago|0 comments
6.
by tschottdorf 9y ago
https://github.com/uwplse/verdi is a good example of this (it uses coq and extractions along with minimal glue).
7.
by tschottdorf 9y ago
employee here. Yep, we've also had our share of troubles with noisy clock on cloud environments, so that's something we're very aware of. Further down the road, we're considering a "clockless" mode, which of co
8.
by tschottdorf 9y ago
I'm not really on wifi good enough to reply extensively, but I pushed an update to the post explaining this better. If you carry out the read explicitly, you can still get the anomaly in much the same way. I should've done so from
9.
by tschottdorf 9y ago
I don't think that gryadka is correct, see http://tschottdorf.github.io/if-its-not-paxos-its-probably-w... .
10.
by tschottdorf 10y ago
Yes, if your timestamp is far enough in the past (this is determined by the maximum clock offset configured for the cluster), and if you don't collide with writes of a long-running transaction (which may run at a timestamp that could i
11.
by tschottdorf 10y ago
Cockroach Labs employee here. We provide serializable consistency for the whole keyspace. It's just that it's easier when you stay in one Raft ensemble as less can go wrong.
12.
by tschottdorf 10y ago
Employee here - which discussion around NewSQL would you like to have? You pay for the consistency in more round trips between replicas, and you need a quorum of your nodes (which carry your data) to be alive. All of that stuff can be made
13.
Creating a Digestible GitHub Digest(cockroachlabs.com)
8 points by tschottdorf 10y ago|0 comments
14.
Adventures in Performance Debugging(cockroachlabs.com)
8 points by tschottdorf 11y ago|0 comments
15.
Living Without Atomic Clocks(cockroachlabs.com)
143 points by tschottdorf 11y ago|48 comments
16.
by tschottdorf 11y ago
Note that Spanner always waits out the clock uncertainty on commit, while Cockroach doesn't need to do that - by design there are fewer situations in which the offset really matters. We can still benefit from a good bound in some situa
17.
by tschottdorf 11y ago
Exactly right. The hard part is building a key-value store with a powerful notion of transactions (not just compare-and-set or the like), and that's what's mostly done. Structured data is still work, but on the shoulders of giants
18.
by tschottdorf 11y ago
The plan is to get out of alpha as soon as possible. I'll leave it to the founders to throw dates around but we're working hard on getting the technical core on solid ground, and all the auxiliary stuff (UI, deployment, ...) requi
19.
by tschottdorf 11y ago
Cockroach trusts the MaxOffset, and if your clocks don't live up to the promise, you might get some stale reads. By the way, Spanner breaks in the same way if their clock offset (via their TrueTime API) fails them. But Spanner has to w
20.
by tschottdorf 11y ago
That's correct, it's a consistent system and so the majority needs to be involved on mutating writes. Reads typically can read from one designated copy of the replica directly (bypassing Raft).
21.
by tschottdorf 11y ago
not quite ready yet, but the pace has picked up dramatically. We've begun work on the structured data layer and are whipping up a suite of extensive acceptance tests (load testing, performance metrics, ...) to iron out all of the perfo