dastbe

23 ms·

211.
by dastbe 5y ago
(i work at aws) so the name qldb is actually from an internal database that inspired the public offering. in naming that, the focus was around the quantization of individual changes (the minimum amount of data necessary!) in a ledger. hence
212.
by dastbe 5y ago
> And partner with credit cards to give it away for free yeah, with dashpass being free for the entirety of the pandemic if you had the top chase card, having a lower mimimum, and lowering fees by more compared to eats pass its really ha
213.
by dastbe 5y ago
Savings is probably confusing here, because savings change based on your socioeconomic position. People go from not saving anything, to saving cash, to saving in assets. Some of these assets have a poorer counterparty who is getting access
214.
by dastbe 5y ago
While I get that this is a public facing post-mortem and won't be as detailed as whatever is provided internally, it doesn't sound like there's any investigation into how such failures in the future can be better contained. T
215.
by dastbe 5y ago
Amazon (like a lot of others) use several CDNs for redundancy. You can see from dig that it resolves to combinations of cloudfront, akamai, and (presumably, based on your reported experience) fastly. dig +short www.amazon.com tp.47cf2
216.
by dastbe 5y ago
What do yall see as the next devx improvements beyond branching and no-fear schema migrations? I'd be really interested in how you might apply the workflows you're defining towards (IMO) bigger problems like data migration and bac
217.
by dastbe 5y ago
(i work at aws) yes, while in my opinion most services won't care about the distinction between cross-az/same-az (you're definitely not most services :) ), you can definitely tell the difference between * in the same region v
218.
by dastbe 6y ago
> Normal Lambda are currently billed in 100ms increments. Lambda actually reduced their billing granularity to 1ms at Re:invent 2020. if anything, Lambda Edge is trailing :).
219.
by dastbe 6y ago
Just wanted to say thanks for the responses. I've forwarded this comment chain over to some people who are interested in this space.
220.
by dastbe 6y ago
(I work at AWS) > I still, frankly, trust Google's Security more than Amazon's If you have the time, could you expand on this? While I'm not directly involved in security at AWS, I'd be down to forward your thoughts t
221.
by dastbe 6y ago
(also work at aws) i think that spoiler alert is a little overgeneralized. first, there’s plenty of advances in those categories in the past 5 or so years (lambda, fargate, qldb, a bunch more) that move the needle significantly on the versi
222.
by dastbe 6y ago
It wasn't a suggestion of replacement, it was saying that even the closest instance still doesn't get you 24TB of on-host storage, having to use EBS instead.
223.
by dastbe 6y ago
disclosure: I work at AWS You're not required to contribute with your amazon e-mail address, and I see a lot of people who don't due to inertia or because they want to avoid tying their identity their employer.
224.
by dastbe 6y ago
(I work at AWS, but this is just for fun) Checking out AWS side, the closest I think you'd get is the x1.32xlarge, which would translate to 128 vCPU (which on intel generally means 64 physical cores) and close to 2TB of RAM. nvme stora
225.
by dastbe 6y ago
I'm not trying to argue the Parler ban or at what percentage does it transition from people caused this to the platform caused this. What I am arguing against is the out-and-out misinformation campaign that zero people who used parler
226.
by dastbe 6y ago
1. Do you earnestly believe the people around the Capitol were "sucking on their soda pops" during a large protest? As someone whose been around several protests in Seattle, there's an overwhelmingly small number of people th
227.
by dastbe 6y ago
> At no time did I see even a single post advocating violent overthrow of the government, white supremacy, etc. Apparently, neither did any of those planning the Capital attack, since they were not Parler members. how do you reconcile th
228.
by dastbe 6y ago
for what its worth, there is a much better scoped ViewOnlyAccess managed policy that makes a much better distinction about what is reasonable read-only access (ecs:listClusters) and not reasonable read-only access (dynamodb:Query)
229.
by dastbe 6y ago
finally getting to see a demo of this, and all I have to say is freakin' boom
230.
by dastbe 6y ago
you’d have to build that into your system, or build a synchronous system in front of you queue to provide these semantics. and does critical imply time sensitivity, necessity of delivery, or both?
231.
by dastbe 6y ago
> Re. size the main examples I'm looking at are SQS, Google's Pub/Sub etc which are pretty hard to fill up or overload. It's not the size of the queue supported by the queue service that's the problem, it is the
232.
by dastbe 6y ago
while this is a good overview, i think this article paints too rosy a picture of message queues, specifically > We can put as many messages as we want into the tube (let's assume we have a infinitely long tube) at whatever speed is
233.
by dastbe 6y ago
(i work at aws) fwiw, a quick google search for `s3 price reduction` yields one from 2016: https://aws.amazon.com/blogs/aws/aws-storage-update-s3-glaci... there's also one-zone s3 storage options which are ch
234.
by dastbe 6y ago
do you have a link to the design doc? EDIT: for those searching, I suspect its https://docs.google.com/document/d/1moQfNcEIttsk6vYanNKIy3Zu...
235.
by dastbe 6y ago
What makes Amazon's multirepo setup "tick" isn't the multirepos themselves but the coordination mechanisms around it (version sets, brazil, and pipelines). whereas bazel/buck are open source and work ok enough to sc
236.
by dastbe 6y ago
How long it takes for work to have impact depends greatly on the scope of that work and the level of abstraction you're viewing the work at. Part of the problem here is the place in the blog ascribes value to where you are rather than
237.
by dastbe 6y ago
The 3 years he quotes is from his perspective, which is from the view of "what company-spanning initiatives are we going to tackle" or "what teams and projects do we need to bootstrap or expand on?". It takes years for t
238.
by dastbe 6y ago
I also wonder how many people aren't realizing just how much they're devoting to subscriptions, especially those with dark patterns where they sign you up for a 1-3 month introductory rate and then jack up the price significantly
239.
by dastbe 6y ago
As the other commenter mentioned, the machines have completely different setups so I don't think you can make any comparative judgment. I also don't work on Azure which is used in that benchmark, and the link I provided was specif
240.
by dastbe 6y ago
(i work at aws) it depends on what you’re talking about. in the context of this article, brendan gregg measured the overhead on nitro as less than 1%. http://www.brendangregg.com/blog/2017-11-29/aws-ec2-virtuali...

More ›