Viewing profile — lizthegrey

The only place where my doxx is "mirrored" right now is KF.

We're paid decent enough for SF bay startup salaries. Worldwide, regardless of where we live/work. This works out quite advantageously for having a distributed workforce, and means…

Part 1 discussion: https://news.ycombinator.com/item?id=36721080

He has the ability to update the HTML on the page to be more specific if he so chooses, he doesn't need the entire forum backend to do so. I'm waiting...

Amazon has made substantive contributions to OpenTelemetry. Which, I suppose increases consumption of AWS in a roundabout way by ensuring people will not have a crashy, buggy mess …

Here's some x86 vs arm comparisons from 2020 substantiating "20% faster and 20% cheaper" -- https://www.honeycomb.io/blog/observations-on-arm64-awss-ama... AWS isn't offering steep…

us-east-1 only for now.

We have real-world performance results here: https://www.honeycomb.io/blog/present-future-arm-aws-gravito... Oh, and btw, we're a ~100% Graviton2/3 shop now!

Ask your observability provider about PrivateLink, or talk to your account rep at AWS about discounting traffic. But also, you can sample some of the data within your own VPCs (see…

Intel charges a much larger markup per chip than AWS can get from their own silicon + licensing ARM IP; the power consumption of Intel chips is also terrible (it's been cited that …

Ah, https://github.com/circonus-labs/fq It was less mature in 2016 when we made the original technology choice (and is still, I'd say, probably not a Boring Technology today). With…

Intel looks less bad when you compare one physical core to one physical core, but AWS definitely will not sell you one physical Intel core for the price of one ARM core, they will …

right -- the question I and others have is, can you convert an existing topic in place or do you have to do the dual-writer/shadow launch, then drain the old one model etc.

In 2016 when we were founded, Pulsar wasn't a thing yet. Today, we'd be very likely to use Pulsar if we were starting from scratch.

Yup! In fact, we collaborate with Datadog, New Relic, Splunk, Lightstep, et al on OpenTelemetry ( https://news.ycombinator.com/item?id=28997275 / opentelemetry.io)

Yup, we went with fewer, higher throughput partitions for this exact reason of wanting precise control over partitioning. It's been a blessing and a curse.

It would be for GCP based customers, but we are a telemetry platform and making our (majority) AWS based customers pay 0.08 per GB to egress to us is a non-starter for them :/

Oh, believe me, we have hired Corey Quinn (Duckbill Group). AWS budged on some things, but not on the EBS cost.

1.5M messages/sec, average message size 1kb pre compression, 300 bytes post compression/batching. the problem was that we were really really disk limited before for keeping the 48 …

The current OSS work is happening here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-405%3A... The proprietary Confluent stuff is here: https://www.confluent.io/blog/infin…