https://tsdr.uspto.gov/#caseNumber=98324800&caseSearchType=U...
Introducing S2
111–120 of 206 posts
Re: Introducing S2
#112Re: Introducing S2
#113Earlier 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…
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
#114IANAL,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...
Re: Introducing S2
#115Re: Introducing S2
#116This 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
#117Help 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.
Re: Introducing S2
#118Earlier quoted context omitted.
(Founder) We are not charging in preview. At the scale where it matters, we will work it out. Definitely some assumptions in here.
Do you plan to charge differently for bandwidth depending on whether the customer is in AWS or not? Would be nice if you pass on the cost savings.
Re: Introducing S2
#119Re: Introducing S2
#120IANAL,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...
Having to rebrand your product after launching is a lot more painful than doing it before launching.