shikhar

10 ms·

91.
by shikhar 2y ago
(Founder) so many possibilities! That's what I love about building building blocks. I think we will create an open source layer for an IoT protocol over time (unless community gets to it first), e.g. MQTT. I have to admit I don't
92.
by shikhar 2y ago
(Founder) I understand the concern. However, cloud discounts at scale can be very large, and we are going to share as much of it as we reasonably can.
93.
by shikhar 2y ago
(Founder) Named pipe that operates at the level of records, is durable regionally, you can read from any sequence, and lets you do concurrency control for writes if you need to.
94.
by shikhar 2y ago
(Founder) we do intend to be multi-cloud, we are just starting with AWS. Our internal architecture is not tied to AWS, it's interfaces that we can implement for other cloud systems.
95.
by shikhar 2y ago
thank you for the feedback!
96.
by shikhar 2y ago
@agallego Yes in aggregate both Confluent and Redpanda can push GiBps throughputs, and I know Redpanda has amazing perf. I was referring to Redpanda Serverless :) And per-partition i.e. ordered throughput. ED: for some reason I wasn't
97.
by shikhar 2y ago
(Founder) That somewhat summarizes yes :) We take a different approach than WarpStream architecturally too, which allows us to offer much lower latencies. No disks in our system, either.
98.
by shikhar 2y ago
(Founder) Appreciate the feedback. We will try to do a better job on the messaging. It is geared at being a building block for data systems. The landing page has a section talking about some of the patterns it enables (Decouple / Buffe
99.
by shikhar 2y ago
(Founder) I have definitely received that advice before :) - to not seem like a regression from S3. But as an abbreviation for Stream Store, it made sense.
100.
by shikhar 2y ago
(Founder) We are not charging in preview. At the scale where it matters, we will work it out. Definitely some assumptions in here.
101.
by shikhar 2y ago
(Founder) well 50% of our name is different
102.
by shikhar 2y ago
(Founder here) Managed cloud offerings for streaming limit ordered throughput pretty low, e.g. Kinesis at 1 MiBps, Redpanda serverless at 1 MiBps, Confluent's even higher-end clusters at 10-20 MiBps IIRC. If you really need ordering, t
103.
by shikhar 2y ago
(Founder) We want S2 to be focussed on the stream primitive (log if you prefer). There is a lot that can be built on top, which we mostly want to do as open source layers. For example, Kafka compatibility, or queue semantics.
104.
by shikhar 2y ago
Indeed... we sure wish we could have nabbed that crate name, but it was not to be. Our Rust SDK is here https://lib.rs/crates/streamstore
105.
by shikhar 2y ago
(Founder) There is a table on the landing page https://s2.dev/ which hopefully gives a nice overview :) It's like S3, but for streams. Cheap appends, and instead of dealing with blocks of data and byte ranges, you work
106.
by shikhar 2y ago
(Founder) Not currently! We want to explore this.
107.
Designing Serverless Stream Storage(blog.schmizz.net)
4 points by shikhar 3y ago|0 comments
108.
Software infrastructure 2.0: a wishlist (2021)(erikbern.com)
12 points by shikhar 3y ago|0 comments
109.
Designing Serverless Stream Storage(blog.schmizz.net)
7 points by shikhar 3y ago|0 comments
110.
Fighting off faux-serverless bandits with the true definition of serverless(gomomento.com)
1 points by shikhar 3y ago|0 comments
111.
by shikhar 3y ago
I believe TigerBeetle are alluding to their integration of protocol-aware recovery [1], which is a worthy consideration for the log implementation. Yet another engineering concern which can be offloaded. If the disaggregated log integrates
112.
by shikhar 3y ago
Agreed, both Google Cloud Storage and Azure Blob Storage support preconditions. Azure even has leases. S3 is for better or worse the common denominator for systems layering on top of object storage.
113.
The leadership myth in replicated databases (2023)(maheshba.bitbucket.io)
60 points by shikhar 3y ago|3 comments
114.
by shikhar 3y ago
> This new tier is deeply innovative, and Amazon will likely enjoy a monopoly on low latency object storages for the next couple of years. I don't think S3 Express will be lonely that long :) It looks like it already isn't - Az
115.
The leadership myth in replicated databases (2023)(maheshba.bitbucket.io)
1 points by shikhar 3y ago|0 comments
116.
by shikhar 3y ago
It can be used to optimize consensus and transaction protocols. Consensus example - check out Nezha ( https://arxiv.org/abs/2206.03285 ), they came up with an interesting 'Deadline Ordered Multicast' (DOM) prim
117.
Amazon Time Sync Service now supports microsecond-accurate time(aws.amazon.com)
52 points by shikhar 3y ago|23 comments
118.
The disaggregated write-ahead log(blog.schmizz.net)
11 points by shikhar 3y ago|0 comments
119.
The disaggregated write-ahead log(blog.schmizz.net)
2 points by shikhar 3y ago|0 comments
120.
What we talk about when we talk about System Design(maheshba.bitbucket.io)
4 points by shikhar 3y ago|0 comments

More ›