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

101–110 of 206 posts

Re: Introducing S2

#101

Post by shikhar »

jcrites wrote: post #70
shikhar wrote: post #35

Earlier quoted context omitted.

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

I think they're saying that you should provide some example use-cases for how someone would use your service. High-level use-cases that involve solving problems for a business. For what it's worth, I am already familiar with this design space well enough that I don't need this kind of example in order to understand it. I've worked with Kinesis and other streaming systems before. But for people who haven't, an example…

(Founder) Yes I understand, and this could definitely do with work. I struggle with it personally because it is so obvious to me. I don't even know where to start? How do you pitch use cases for object storage? Stream storage feels just as universal to me.

Re: Introducing S2

#102

Post by evantbyrne »

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.

Re: Introducing S2

#103

Post by shikhar »

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 be self-hosted, with features like client-side encryption so you can have even more peace of mind.

Re: Introducing S2

#104

Post by everfrustrated »

shikhar wrote: post #69
8n4vidtmkvmk wrote: post #38

Earlier quoted context omitted.

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

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

Discounts require multi year commitment for minimum (and increasing) spend. Generally you need to be either profitable or a well funded startup to demonstrate why a vendor would trust your ability to pay (it's literally a debt on your books). How do they know you're good for it?

Plus multi cloud means less scale and less marketing incentive (can't talk about you as a x cloud customer).

I wish you the best, but would encourage you to not set your prices below your costs.

Re: Introducing S2

#106

Post by evantbyrne »

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…

First-class kafka compatibility could go a long way to making it a justifiable tech choice. When orgs go heavy on event streaming, that code gets _everywhere_, so a vendor off-ramp is needed.

Re: Introducing S2

#107

Post by nextworddev »

This is cool but I think it overlaps too much with something like Kinesis Data Streams from AWS which has been around for a long time. It’s good that AWS has some competition though

Re: Introducing S2

#108

Post by shikhar »

everfrustrated wrote: post #104
shikhar wrote: post #69

Earlier quoted context omitted.

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

Discounts require multi year commitment for minimum (and increasing) spend. Generally you need to be either profitable or a well funded startup to demonstrate why a vendor would trust your ability to pay (it's literally a debt on your books). How do they know you're good for it? Plus multi cloud means less scale and less marketing incentive (can't talk about you as a x cloud customer). I wish you the best, but would…

(Founder) Thank you for the advice. I hope we can offer better when the deals come into play, but for now setting our planned internet egress price to $0.08/GiB.

Re: Introducing S2

#110

Post by shikhar »

MicolashKyoka wrote: post #78
solatic wrote: 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?

strat is likely just get users, then offboard aws if the product works.

(Founder) No, we want to be in the same cloud regions as customers.
Post reply on HN