Viewing profile — ryanworl
ryanworl
HN member- Joined
- Sat, Dec 15, 2012, 6:33 PM UTC
- HN karma
- 1,454
- Public activity
- 432 items
- HN profile
- View on Hacker News ↗
About ryanworl
ryantworl@gmail.com
Recent public activity
- story
-
comment
Comment #44111167
Does this trick preclude the ability to sort your data within a partition? You wouldn’t be able to rely on the row IDs being sequential anymore to be able to just refer to a prefix…
-
comment
Comment #43765284
This is a well-known class of optimization and the literature term is “late materialization”. It is a large set of strategies including this one. Late materialization is about as o…
- story
-
comment
Comment #43539122
The equivalent to this feature is one of my favorite parts of Husky, Datadog’s storage and query system for event data. https://youtu.be/mNneCaZewTg?si=N68fsBlYS3tuvLe3 begins at 3…
- story
-
comment
Comment #40200154
We're still drafting our next post in this series, but the answer is actually very simple: two tiers of object storage do not have the same drawbacks as a combination of object sto…
-
comment
Comment #40199940
This strategy will not work well for Apache Kafka because it is extremely IOPS hungry if you have more than a few partitions, and a replay of a large topic will require lots of IO …
-
comment
Comment #40199614
(WarpStream co-founder here) We're not talking about no disks as in no storage, just nothing other than object storage. This does have a latency trade-off, but with the advent of S…
- story
- story
-
comment
Comment #38450097
Co-founder of WarpStream here. We wrote a short article explaining how the economics of this new storage class work for a system like ours: https://www.warpstream.com/blog/s3-expre…
- story
-
comment
Comment #38350826
WarpStream co-founder here. Implementing the Idempotent Producer feature for the Apache Kafka protocol was definitely a fun challenge for us. Please let me know if you have any que…
-
comment
Comment #37847089
[WarpStream co-founder] WarpStream doesn't implement compacted topics today. It is on our roadmap, though. Compacted topics are typically not used in high-throughput workloads, so …
-
comment
Comment #37054348
[WarpStream CTO here] WarpStream flushes after 4MiB of data or a configurable amount of time. Flushes can also happen concurrently. In general, we'd prefer to not introduce many kn…
-
comment
Comment #37049487
[WarpStream CTO here] I'm not going to respond to your comment directly (we've already solved all the problems you've mentioned), but I thought I should mention for the sake of the…
-
comment
Comment #37040053
We're aiming for per-GB usage-based pricing that is significantly cheaper than the alternatives, but the BYOC model combined with our extremely efficient cloud control plane gives …
-
comment
Comment #37039699
[WarpStream co-founder here] Please sign up for our mailing list! We'll have some interesting things to announce related to this soon.
-
comment
Comment #37039486
With an appropriately configured client (i.e. one that retries and waits for requests to be acknowledged), another Agent would receive the retry and the event would be written to t…
-
comment
Comment #37039445
[WarpStream co-founder here] We've done lots of customer research here and, combined with the experience my co-founder and I have, we can confidently say most Kafka users (especial…
-
comment
Comment #37038978
[WarpStream co-founder here] My co-founder and I worked at Datadog for over 3 years where we built Husky, an event storage and query system built directly on top of S3 as well. We …
-
comment
Comment #37038864
[WarpStream CTO here] WarpStream is Kafka protocol compatible, so we do support topic-partitions and consumer groups. We do not expose support for transactions or idempotent produc…
-
comment
Comment #37037690
(WarpStream CTO here) This is a bit subtle I will admit, but we view the Kafka protocol as a successor here because it will outlive Kafka the implementation.
-
comment
Comment #37037114
[WarpStream co-founder here] That is correct about flushing. RE: consuming. The TLDR; is that the agents in an availability zone cluster with each other to form a distributed file …