51–60 of 114 posts
Kudos on the work done and I hope you the best of luck. A little note of advise: I wouldn’t start my company description as “the Y of X” or “the Y alternative to X”. It’s okay to mention if you are similar to another well known company, but don’t use it to describe your company, specially not in the first line.
I agree. I hadn't heard of Segment and now I'm reading your competitors website.
Overall, I like this recent trend a lot - more companies are building open-source, lightweight, GDPR compatible analytics, chats (e.g. Papercups). I hope there will be good ways to monetize and sustain this. Wish you all the best, folks!
I really like this, congratulations on the launch. And this is such a huge space that there's definitively room for other options (aside from Segment). I'm a little bit out of the loop in this event processing space. Do you think Jitsu could replace lower-level event processing implementations as Kafka/Kinesis? Or this is thought for more "high level" marketing stuff.
That's a good question. We're aiming to replace Kafka in some cases. There're many ways how people use Kafka. But it could be roughly divided into two buckets - Kafka as a company wide message bus: dozen's of (micro)services sending data there, and consumers listens to data. Each service doesn't know which other service will consume the data. For that case, we're not looking to replace Kafka — we're going to work alo…
How are your handling data between collection agents and storage? With Kafka, I know what I'm getting when it sits between the two and the advantages it offers.
Please consider posting some form of this as a blog post as well, I love to hear about product inceptions. HN doesn’t allow lesser users with lesser eyesight to read light grey on beige self text, unfortunately.
Earlier quoted context omitted.
That's a good question. We're aiming to replace Kafka in some cases. There're many ways how people use Kafka. But it could be roughly divided into two buckets - Kafka as a company wide message bus: dozen's of (micro)services sending data there, and consumers listens to data. Each service doesn't know which other service will consume the data. For that case, we're not looking to replace Kafka — we're going to work alo…
> We're aiming to replace Kafka in some cases How are your handling data between collection agents and storage? With Kafka, I know what I'm getting when it sits between the two and the advantages it offers.
Earlier quoted context omitted.
Disclaimer: Haven't looked at Jitsu in depth so my understanding below may be limited. Reading through their comment below - "Jitsu can be used for any kind of data while Segment compatibility is just a thin layer on top". I am guessing they have built a generic event API that can be used to send any JSON payload while RudderStack (like Segment) has a opinionated view of events - e.g. there has to be a userID (or ano…
We have suggested event structure ( https://github.com/jitsucom/jitsu/blob/master/javascript-sdk... ). If you want to send data to destination, you should either follow suggested structure or write your own JavaScript mapping ( https://jitsu.com/blog/javascript-transform ). And we have DBT models too https://hub.getdbt.com/jitsucom/jitsu/latest/ !
jitsu_sessionization_trailing_window: 3
jitsu_session_inactivity_cutoff: 30 * 60
Earlier quoted context omitted.
We have suggested event structure ( https://github.com/jitsucom/jitsu/blob/master/javascript-sdk... ). If you want to send data to destination, you should either follow suggested structure or write your own JavaScript mapping ( https://jitsu.com/blog/javascript-transform ). And we have DBT models too https://hub.getdbt.com/jitsucom/jitsu/latest/ !
Is that dbt project also doing the sessionization? I see this: jitsu_sessionization_trailing_window: 3 jitsu_session_inactivity_cutoff: 30 * 60 EDIT: No idea why valid reply from dev is marked dead, but thanks! Really, really cool that you're using dbt for this process.