Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing S2

s2.dev

Post reply on HN
Print view View original

141–150 of 206 posts

Re: Introducing S2

#141

Post by yandie »

shikhar wrote: post #17
stogot wrote: 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…

Hey congrats! Looks like a really cool idea.

Looks like you're pushing for the throughput angle - that could be important but IMO it's not often you come across devs who need this level of throughput without dealing with large scale problem. My feedback is the lack of per-tenant encryption is a big deal breaker here since you're mixing up data of tenants within one objects.

Plus your security section talks very little how you prevent cross data contamination - that's probably first thing that popped up in my mind when I read about your data model. It makes me extremely uneasy - and can't imagine that I can adopt this for anything serious. I would encourage you to think about how you can communicate that angle to the customer as well, besides supporting per tenant encryption key.

Re: Introducing S2

#142

Post by hipadev23 »

skeeter2020 wrote: post #127
volemo wrote: post #114

Earlier quoted context omitted.

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

S3++ ? T4? My company is a Fivetran client, and they named that company after a (bad) joke, but it's worth a fortune.

Fivetran is going to zero because they don’t offer anything of actual value and their CEO isn’t a good person.

[1] https://news.ycombinator.com/item?id=42434450

Re: Introducing S2

#143

Post by Too »

_1tem wrote: post #54

This is a really good idea, beautiful API, and something that I would like to use for my projects. However I have zero confidence that this startup would last very long in its current form. If it's successful, AWS will build a better and cheaper in-house version. It's just as likely to fail to get traction. If this had been released instead as a Papertrail-like end-user product with dashboards, etc. instead of a "clo…

They just did https://news.ycombinator.com/item?id=42211280 (Amazon S3 now supports the ability to append data to an object, 30 days ago). Azure has had the same with append blobs for a long time. It's still a bit more raw than S2, without the concept of record. The step for a cloud provider to offer this natively is very small. And with the concept of a record, isn't this essentially a message queue, where the competitor space is equally big? Likewise if you look into log storage solutions.

Re: Introducing S2

#144

Post by soorya3 »

volemo wrote: post #114
animex wrote: 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...

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

F3 - (Fast Furious Fail-Safe)

Re: Introducing S2

#146

Post by rswail »

shikhar wrote: post #27
do_not_redeem wrote: post #26

Earlier quoted context omitted.

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

(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.

S3++?

Re: Introducing S2

#147

Post by rswail »

thaumasiotes wrote: post #21
jsheard wrote: post #19

Earlier quoted context omitted.

How many of these letter-number storage services are there now? S3, B2, R2, S2...

S3 isn't the name of the service - that's "Amazon Simple Storage Service". S3 is a nickname, short for "Simple Storage Service".

and EC2 stands for "Elastic Compute Cloud". but no one remembers that.

Re: Introducing S2

#148

Post by rswail »

shikhar wrote: post #103
evantbyrne wrote: post #102

Seems like really cool tech. Such a bummer that the it is not source available. I might be a minority in this opinion, but I would absolutely consider commercial services where the core tech is all released under something like a FSL with fully supported self-hosting. Otherwise, the lock-in vs something like kafka is hard to justify.

(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.

Re: Introducing S2

#149

Post by rswail »

bushido wrote: 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…

"Replace our MSK clusters and EBS storage with S3 storage costs."

Re: Introducing S2

#150

Post by rswail »

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.

Post reply on HN