Live data from Hacker News

Show HN: RudderStack, open-source CDI (a.k.a. open-source Segment)

news.ycombinator.com

11–20 of 41 posts

Re: Show HN: RudderStack, open-source CDI (a.k.a. open-source Segment)

#11

Earlier quoted context omitted.

Yes, very recently did we switch from SSPL to AGPLv3 (as noted in updates above)

But the repo says SSPL... in the readme & in the LICENSE file isn't that the source of truth? Or what matters to an organization evaluating adoption?

@soumyadeb - can't reply another level deep here. I'll create an PR in the repo.

https://github.com/rudderlabs/rudder-server/pull/183

Cool project!

Re: Show HN: RudderStack, open-source CDI (a.k.a. open-source Segment)

#12

Earlier quoted context omitted.

But the repo says SSPL... in the readme & in the LICENSE file isn't that the source of truth? Or what matters to an organization evaluating adoption?

@soumyadeb - can't reply another level deep here. I'll create an PR in the repo. https://github.com/rudderlabs/rudder-server/pull/183 Cool project!

Thanks for the pull request :) Merged...

Re: Show HN: RudderStack, open-source CDI (a.k.a. open-source Segment)

#13

Earlier quoted context omitted.

But the repo says SSPL... in the readme & in the LICENSE file isn't that the source of truth? Or what matters to an organization evaluating adoption?

Thanks for pointing it out. The LICENSE file was old, removed it now. The README says AGPLv3. Or am I missing something?

[deleted]

Re: Show HN: RudderStack, open-source CDI (a.k.a. open-source Segment)

#15
Is this suitable if I want to stream events (e.g. click event data), around 1k events/per sec, to a Redshift database, and see it happen realtime? Redshift should receive the data within 5-20 minutes.

Will rudderstack work for this usecase? Or will it require something in between.

Re: Show HN: RudderStack, open-source CDI (a.k.a. open-source Segment)

#16

Is this suitable if I want to stream events (e.g. click event data), around 1k events/per sec, to a Redshift database, and see it happen realtime? Redshift should receive the data within 5-20 minutes. Will rudderstack work for this usecase? Or will it require something in between.

Yes, this is a very standard use case. A single node RudderStack (m4.xlarge) should be able to process more than 1K/sec. And Redshift should receive the data in 30 mins (configurable parameter).

Please give it a shot. Email me soumyadeb@rudderlabs.com if you run into any issues.

Re: Show HN: RudderStack, open-source CDI (a.k.a. open-source Segment)

#17
post #14

what is your k8s strategy?

We use helm charts to deploy Rudder. Repo here https://github.com/rudderlabs/rudderstack-helm

We have 3 separate pods - one for the RUdder core BE, one for the transformation (javascript which map events from Rudder format to destination format as well as user defined transformations) and one running Postgres.

Re: Show HN: RudderStack, open-source CDI (a.k.a. open-source Segment)

#19

Founder here - happy to answer any questions

It's not really clear to me what it does, seems like a bus for data, but how is it related to kafka for example? sorry if it's too silly, I'm a bit lost, and I think it may be useful to me. I've checked segment's website and some of their stuff like unified view of a customer may be useful to me. Regards

Re: Show HN: RudderStack, open-source CDI (a.k.a. open-source Segment)

#20
post #19

Founder here - happy to answer any questions

It's not really clear to me what it does, seems like a bus for data, but how is it related to kafka for example? sorry if it's too silly, I'm a bit lost, and I think it may be useful to me. I've checked segment's website and some of their stuff like unified view of a customer may be useful to me. Regards

That's right. What we have today is more of a bus but for customer event data.

Let's say you have a website or mobile app and you want to collect all the user interaction events (clicks, searches, impressions) in a data-warehouse like Snowflake.

RudderStack can do it for you. We have SDKs (Android, iOS, JS, Python etc) which you can use to send events. We have a corresponding backend (you can run it or we can host it) which will collect these events and dump into your warehouse.

You often want to send (subset of these) events to other 3rd party websites too like Amplitude for analytics, Braze for marketing automation and so on. RudderStack can forward events to those too so you don't have to embed multiple 3rd party SDKs and understand their library etc.

The second part of this is to create a unified view of the customer as you mentioned and take action on that (e.g. find all churning users and send them email). That's where Segment has a product called Personas and we are working on something similar but it's not launched yet.

Though even before, you can build that customer view on top of your event data in your data warehouse by using SQL or a tool like Looker. For example, you find all churning users by writing a simple SQL query. And then send that result by something like Looker Action Hub.

Happy to discuss more here or offline (email: soumyadeb@rudderstack.com)

Post reply on HN