Live data from Hacker News

Introducing S2

s2.dev

31–40 of 206 posts

Re: Introducing S2

#34
post #18

Earlier quoted context omitted.

(Founder) well 50% of our name is different

You should have gone with S4 tbh. The suits love bigger numbers. Super Simple Stream Store.

Disagree. You have a marketing opportunity for a hipster character named "Stu" to be the spokesman.

Re: Introducing S2

#35
post #23

I wish more dev-tools startups would focus on clearly explaining the business use cases, targeting a slightly broader audience beyond highly technical users. I visited several pages on the site before eventually giving up. I can sort of grasp what the S2 team is aiming to achieve, but it feels like I’m forced to perform unnecessary mental gymnastics to connect their platform with the specific problems it can solve fo…

(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 / Buffer / Journal) in a serverless manner, with example use cases. It just may not be something that resonates with you though! We are interested in adoption by developers for now.

Re: Introducing S2

#36
post #11
post #7

[flagged]

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

Replying to this one since you apparently can't reply to a comment that has been flagged. Why was the grandparent flagged? Google's S2 library has been around for more than a decade and is the first thing I think of when I see "S2" in a tech stack.

And the flippant response from the parent here that they don't really care that they're muddying the waters and just want the crate name is irksome.

Re: Introducing S2

#37
This is a very interesting abstraction (and service). I can’t help but feature creep and ask for something like Athena, which runs PrestoDB (map reduce) over S3 files. It could be superior in theory because anyone using that pattern must shoehorn their data stream (almost everything is really a stream) into an S3 file system. Fragmentation and file packing become requirements that degrade transactional qualities.

Re: Introducing S2

#38
post #22
post #20

Help me understand - you build on top of AWS, which charges $0.09/GB for egress to the Internet, yet you're charging $0.05/GB for egress to the Internet? Sounds like you're subsidizing egress from AWS? Or do you have access to non-public egress pricing?

(Founder) We are not charging in preview. At the scale where it matters, we will work it out. Definitely some assumptions in here.

Just FYI, that doesn't give me confidence in the longevity of your service.

Re: Introducing S2

#39

These folks knowingly chose to spend the rest of their careers explaining that they are not, in fact, S3.

Including potentially in court / to lawyers? IANAL, but isn't this just inviting Amazon to claim it's deliberately leveraging their 'S3' trademark and sowing confusion in order to lift their own brand? (Correctly, and even somewhat transparently in TFA, IMO.)

Re: Introducing S2

#40
post #17
post #13

Earlier quoted context omitted.

Could you clarify the Kafka difference further? Or more generally, when is it better to choose S2 vs services like SQS or Kinesis? S2 sounds like an ordered queue to me, but those exist?

(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, this can indeed be a limit. S2 lets you push 125 MiBps currently, and we may grow that. Another factor is how many ordered streams you can have. Typically a few thousand at most with tho…

Between your site copy and your early comments on this thread, it was this rundown that made the product click in my mind.

I’m sure that in this early preview you’re trying to reach mainly devs with existing domain expertise, but the way that, in this comment, you laid out existing constraints and what possibilities might lie beyond them—it really helped me situate your S2 product in the constellation of cloud primitives.

Just wanted to offer that feedback in the hope that the spirit of your comment here doesn’t get buried down-thread!

Post reply on HN