Live data from Hacker News

Introducing S2

s2.dev

161–170 of 206 posts

Re: Introducing S2

#161
post #114

Earlier quoted context omitted.

TBF, building something with the goal of enhancing S3 I would call it S4.

Thats short term thinking. you need to leapfrog everybody and go s∞

That’s actually a pretty cool name if you pronounce the first letter the letter sound rather than as an initial: Sinfinity

Re: Introducing S2

#162
post #150

Really interesting service and bookmarked. I'd really love this extending more into the event sourcing space not just the log/event streaming space. Dealing with problems like replay and log compaction etc. Plus things like dealing with old events. Under GDPR, removing personal information/isolating it from the data/events themselves in an event sourced system are a PITA.

(Founder) An S2 stream is a durable log and can be replayed! We do want to add compaction support. Event sourcing is a great use case for S2.

Re: Introducing S2

#163

I look at the egress costs to internet and it doesn’t check out. It’s a premium product dependent on DX, marketed to funded startups. But if I care about ingress and egress costs, which many stream heavy infrastructure providers do.. This doesn’t add up. I wish them luck, but I feel they would have had a much better chance from the start by getting some funding and having a loss leader start, then organising and pass…

(Founder) Thanks for sharing your thoughts. We are early and figuring things out. I agree egress cost is going to be a big concern. We want to do the best we can for users as we unlock some scale. During preview, we are focused on getting feedback so the service is free (we will need to talk if the usage is significant though).

Re: Introducing S2

#164
post #111

IANAL,but naming your product S2 and mentioning in the intro that AWS S3 is the tech you are enhancing is probably looking for a branding/copyright claim from Amazon. Same vertical & definitely will cause consumer confusion. I'm sure you've done the research about whether a trademark has been registered. https://tsdr.uspto.gov/#caseNumber=98324800&caseSearchType=U...

Yep, letter S and a number is copyrighted, can't do that

Re: Introducing S2

#165
post #148

Earlier quoted context omitted.

(Founder) We are happy for S2 API to have alternate implementations, we are considering an in-memory emulator to open source ourselves. It is not a very complicated API. If you would prefer to stick with the Kafka API but benefit from features like S2's storage classes or having a very large number of topics/partitions or high throughput per partition, we are planning an open source Kafka compatibility layer that can…

Having a kafka compatible API and S3 storage would be something I would jump to, the savings over MSK would be huge. If you had a (paid for) API that sat on top of an S3 API for on-prem, that would be fantastic as well. Kafka is great, but the whole Java ecosystem and the lack of control of what is in the topics and the stuff about co-ordinating the cluster in zookeeper is a management PITA.

Checkout warpstream (recently acquired by confluent)

Re: Introducing S2

#166
post #161

Earlier quoted context omitted.

Thats short term thinking. you need to leapfrog everybody and go s∞

That’s actually a pretty cool name if you pronounce the first letter the letter sound rather than as an initial: Sinfinity

Sounds more like a porn website...

Re: Introducing S2

#168
post #111

IANAL,but naming your product S2 and mentioning in the intro that AWS S3 is the tech you are enhancing is probably looking for a branding/copyright claim from Amazon. Same vertical & definitely will cause consumer confusion. I'm sure you've done the research about whether a trademark has been registered. https://tsdr.uspto.gov/#caseNumber=98324800&caseSearchType=U...

Fun fact: S2 and EC2 sound exactly the same in Spanish - both are "ese dos". Add that to EC2 and S3 already being confusing to tell apart by ear

Re: Introducing S2

#169
post #164
post #111

IANAL,but naming your product S2 and mentioning in the intro that AWS S3 is the tech you are enhancing is probably looking for a branding/copyright claim from Amazon. Same vertical & definitely will cause consumer confusion. I'm sure you've done the research about whether a trademark has been registered. https://tsdr.uspto.gov/#caseNumber=98324800&caseSearchType=U...

Yep, letter S and a number is copyrighted, can't do that

1) we're talking about trademark law, not copyright law.

2) the problem here is that they're in the same business segment, and explicitly reference S3.

Re: Introducing S2

#170

Earlier quoted context omitted.

For what it's worth, there's zero chance I would do business with a company whose business plan is "we'll work it out". It gives one every reason to believe that in a couple years time you guys will either be out of business (because you didn't figure out the numbers to make a profit) or will pull the rug from under customers in the form of surprise price hikes. Obviously you have to do what you think is right, but I…

(Founder) We are not charging during preview. If anything, I wanted to be transparent about our planned pricing. Our mission is to make streams a cloud storage primitive, and I worked backwards from there in terms of our costs and expected costs looking ahead once we can scale a bit - based on concrete data points about what kind of discounts can be unlocked. I realized it was premature based on the comments here, so…

[deleted]
Post reply on HN