dastbe

8 ms·

61.
by dastbe 3y ago
PSEs?
62.
by dastbe 3y ago
this was done to support a historically common pattern: people sharing email addresses who still wanted distinct accounts.
63.
by dastbe 3y ago
transaction in the way everyone else here is using it is referring to the primitive provided by the database which gives certain guarantees (depending on isolation level) wrt reads and writes. Even in the context of "transaction"
64.
by dastbe 3y ago
what’s the right way to interpret the last section on cpu utilization? i.e. now that you’re able to achieve 12.5gbps how much overhead is this at a machine level? also was ena express used on the c6i.8xlarge? that should allow for getting p
65.
by dastbe 3y ago
circulating bills don’t have to be in your wallet. 100 dollar bills are primarily used as stores of cash abroad and for illicit wealth. which is why despite the fact you raised people will be skeptical when you try to pay with one.
66.
by dastbe 3y ago
> AWS was the public release of tooling that amazon had been bulding for almost 20 years at that point. No, even at the onset AWS was an entirely-from-the-ground-up build. The only thing it could even be argued to sit on top of was the e
67.
by dastbe 3y ago
they are 14 years old at this point. aws has what, four years on them?
68.
by dastbe 3y ago
at least one cloud provider service over (and sometimes under) charged customers for several years on a particular product due to a misinterpretation of some complex rules. it happens at all orders of magnitude.
69.
by dastbe 3y ago
You're reading it wrong, you need to look at https://www.nyc.gov/site/tlc/about/driver-pay-rates.page for the pay rates. just looking at the per minute numbers, if you worked 60 minutes of P2+P3 time you
70.
by dastbe 3y ago
in that case, yes aws ec2 (and other cloud providers) disable ip spoofing by default for VMs in your VPC.
71.
by dastbe 3y ago
it does depend on what you mean. By 2020/2021, effectively everything was on top of AWS VMs/VPC and perhaps LBs at that point? Most if not all new services were being built in NAWS.
72.
by dastbe 3y ago
where’s the worked examples, forrestbrazeal
73.
by dastbe 3y ago
Could you expand on what you think the different interfaces should be? you keep stating that these things ought to be distinct but haven't explained why beyond dogma.
74.
by dastbe 3y ago
i do recall the simplestack version of dpx had some obscene issues with garbage generation, followed by some obscene issues with throughput due to aggressive locking (to avoid the obscene amount of garbage generated).
75.
by dastbe 3y ago
consistent hashing requires a bunch of additional memory to solve load variance. there's a nice equation to calculate this somewhere that I'd have to search for, but roughly you need 100 virtual slots in your coordinate space per
76.
by dastbe 3y ago
you can run an NLB that terminates v4 and forwards to v6 internally: https://aws.amazon.com/about-aws/whats-new/2020/11/network-l...
77.
by dastbe 3y ago
you reject the message in the framework? and if the client is aware it’s required they fail to send? the bigger challenge with proto3 is that people use it both for rpc and storage, in some cases directly serializing rpc payloads. Disregard
78.
by dastbe 3y ago
i mean the latter (have z builds been allowed in the past decade), and i agree that it’s not fun over the long term but possible and in a lot cases sustainable.
79.
by dastbe 3y ago
So the same is effectively true at Amazon? If a service in a version set isn't actively maintained then it'll eventually be unable to merge from live, and that means its dead code. Version sets do allow for services to exist in a
80.
by dastbe 3y ago
(disclosure: I work at Uber) > There's little reason for drivers to not be on every available platform So yes and no. Yes in the sense that switching costs for a driver are very low, but no in the sense that not all platforms provid
81.
by dastbe 4y ago
> (the slow O^2 solution) whats the fast solution
82.
by dastbe 4y ago
> I do disagree that there are opportunities to benefit from distributed consensus there's some benefits to static stability and grey failure, but sure, whatever. the important bit is to have clear paths of aggregation and dissemina
83.
by dastbe 4y ago
this doesn't paint a full picture of your options, as there's nothing that stops you from having zonal/regional consensus and then replication across regions/long-range topologies for global distribution. to be pithy abo
84.
by dastbe 4y ago
do you mean the cloud provider can't, or the customer can't?
85.
by dastbe 4y ago
I would point out > - GCP will be a cash cow forever, just like AWS and Azure. GCP is still losing something like a billion dollars a year.
86.
by dastbe 4y ago
this is something i've really felt moving from aws to a company that isn't a cloud provider. even when most aws services are third best at best in their category, you still get the following benefits 1. everything works reasonably
87.
by dastbe 4y ago
this is actually quite a lot better these days as the tooling adapts to integrate. go has always been the gold standard, but java/kotlin works very well and js/ts are much improved by rules_js.
88.
by dastbe 4y ago
git log <directory> accomplishes this already.
89.
by dastbe 4y ago
i’ve made this argument before, but you can run a 1k engineering company in a monorepo with the tools and services that exist today. between improvements to bazel (and alternatives) and adjacent tooling like build caching/target diffs,
90.
by dastbe 4y ago
i don’t think they’ve had a console that bleeds money in the sense that playstations/xboxes have, though they’ve had quite a few flops over the past 20 years

More ›