fizwhiz

12 ms·

1.
by fizwhiz 3y ago
I'm sorry but this was easily the most pretentious book I've read all year.
2.
by fizwhiz 3y ago
Why hasn't their stock plummeted like Google's?
3.
by fizwhiz 3y ago
FWIW they mention this at the bottom of their document > Just like BlazingMQ’s other subsystems, its leader election implementation (and general replicated state machinery) is tested with unit and integration tests. In addition, we perio
4.
by fizwhiz 3y ago
> This section explains the leader election algorithm at a high level. It is by no means exhaustive and deliberately avoids any formal specification or proof. Readers looking for an exhaustive explanation should refer to the Raft paper,
5.
by fizwhiz 3y ago
Lots of haters on the part1 segment of this article wondering "wtf does this VP even do?!" > I have friends who are line managers at larger companies who take home more than I do in my current role I wonder if this is the &quot
6.
by fizwhiz 3y ago
What's min-maxing?
7.
by fizwhiz 3y ago
Obligatory: https://danluu.com/sounds-easy/
8.
by fizwhiz 3y ago
These roles likely comprise less than 5% of all engineers at big tech companies so I would be pretty surprised if such a book exists.
9.
by fizwhiz 3y ago
nit: Cockroach was founded by a Xoogler but there's no public evidence that they were on the Spanner team at any point.
10.
by fizwhiz 4y ago
With idempotence, you shift the problem from "deliver X exactly once" to "make it seem like X was delivered exactly once". In most systems, exactly-once is really "effectively exactly once".
11.
by fizwhiz 4y ago
Exactly Once = At least once + Idempotence
12.
by fizwhiz 4y ago
How do you reconcile this with the importance of crosstalk and contention as espoused by the USL? https://wso2.com/blog/research/scalability-modeling-using-un...
13.
by fizwhiz 4y ago
OT: Sorry to hear what happened to you at Twitter (:
14.
by fizwhiz 4y ago
> It’s also important that the loader generates those requests at a constant rate, best done asynchronously, so that response processing doesn’t get in the way of sending out new requests. Coordinated Omission is subtle but deserves more
15.
by fizwhiz 4y ago
Damn dude what did you do? Sell Ads to teens?
16.
by fizwhiz 4y ago
Obligatory memcache scaling paper mention: https://www.usenix.org/system/files/conference/nsdi13/nsdi13...
17.
by fizwhiz 4y ago
Can you walk me through how waiting some amount of time actually improves their guarantee? It's not like they're using Google's TrueTime api that provides bounds on time. How is "unnecessary lag" avoided between Pro
18.
by fizwhiz 4y ago
https://news.ycombinator.com/item?id=31743182#31743198 :)
19.
by fizwhiz 4y ago
From earlier in the article: > Clock skew across different sensors: Sensors might be located across different datacenters, computers, and networks, so their clocks might not be synchronized to the millisecond. And later on in their fina
20.
by fizwhiz 4y ago
> In the US and Europe, RSUs are difficult to get wrong because of share withholding I believe the withholding is 22% by default. If you're living in CA and have a large RSU vest, then your actual tax liability is much higher. Frien
21.
by fizwhiz 4y ago
TIL Edgar Codd went by Ted.
22.
by fizwhiz 4y ago
> both pictures of white male talking to white female. white passing *
23.
by fizwhiz 4y ago
I'm not convinced that issues requests from the multiple clients for the same key actually matters. My speculation is that they map a key to their backend via some type of (consistent/rendezvous) hash and then ensure that all re
24.
by fizwhiz 4y ago
What a ridiculous marketing term. This is a RYW (Read your writes) level of consistency which is a far cry from Strong consistency (see https://jepsen.io/consistency ). Seems like eventual consistency with some affinity bo
25.
Famous outages along with deep postmortems?
24 points by fizwhiz 5y ago|12 comments
26.
by fizwhiz 5y ago
Fond memories of watching that show.
27.
by fizwhiz 5y ago
> buy a third bay area house In palo alto / atherton no less.
28.
by fizwhiz 5y ago
Would you mind describing your stack in more detail? Did you use gRPC with Go?
29.
by fizwhiz 5y ago
I'm guessing they were referring to "Scalability! But at what COST?" https://www.usenix.org/system/files/conference/hotos15/hotos...
30.
by fizwhiz 5y ago
This reminds me of https://en.wikipedia.org/wiki/Thundering_herd_problem

More ›