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

Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative

news.ycombinator.com

Post reply on HN
Print view View original

101–110 of 114 posts

Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative

#104

Post by dominotw »

vklmn wrote: post #49
dominotw wrote: post #38

Is https://meltano.com/ a more general version of this ? i am wondering how this compares to it?

We have some overlap. In simple words: a Singer + DBT, Jitsu is Event Collector + Singer + Airbyte. Meltano will pull data from Singer connectors and do transformations, but they won't run Airbyte connectors, and you can't push data to Meltano Jitsu will use Airbyte or Singer to pull data, and you can push the data to Jitsu. But Jitsu won't run DBT transformation. Although we can trigger DBT cloud jobs: https://jitsu…

that was very clear. thank you!

Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative

#105

Post by xtreding »

tomnipotent wrote: post #90
xtreding wrote: post #86

Earlier quoted context omitted.

Hi! My name is Sergey, I’m a Jitsu product engineer. I’ll gladly answer your question! AsyncLogger works asynchronously by design. There is a go channel which writes JSON’s to the log file. Answering your question: the service doesn’t wait until data is written to the log prior to returning success to the client. WAL log is designed for keeping events JSON’s between Jitsu instance restarts to prevent data loss. When…

Is the WAL only used during restart, or also during normal operations? Trying to create a mental model of how data flows through the system and into destinations.

During normal operations as well. Jitsu supports destinations in two modes: stream and batch. In case of using batch mode: all JSON events will be stored into WAL asynchronously (client doesn't have to wait) and then batch destination processes WAL files in background and stores data in batches. In case of using stream mode: all JSON events will be stored into queue (which is persistent) and will be processed one by one and stored with insert statements into the data warehouse.

Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative

#106

Post by saintfiends »

vklmn wrote: post #99
polskibus wrote: post #98

How do I scale jitsu if the load from my app servers become too big? Will adding more jitsu nodes trample the database nodes that jitsu writes to? How should I plan capacity for a jitsu deployment in a multi node scenario, and what should I take into consideration when scaling it?

Yes, just add more jitsu nodes. It's hard to answer how many nodes do you need (depends on transformations, CPU/RAM/etc), but you can count on thousands request per second per node at least

How is event ordering handled when multiple instances of Jitsu are involved.

Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative

#107

Post by frb »

vklmn wrote: post #75
public_void wrote: post #63

Hey congrats on the launch, clearly a lot of thought and effort went into this. I'm pretty new to this space, and maybe this is a dumb question but how does this differ from Mixpanel? Would I use this for something different?

Mixpanel will store the data for you and do visualization. Jitsu just help you to get you data to your data warehouse. Downside: you'll need to build all visualization by yourself. Fortunately that's easy with tools such as Looker, Mode, Metabase etc Upside: you can do with your data whatever you want - built any reports, join with other datasets etc. You not limited by reports MixPanel team build. In reality, Jitsu…

Feedback on "Jitsu support s MixPanel as a destination"

This is not really clear from the website. Mixpanel is mentioned in https://jitsu.com/sources but NOT in https://jitsu.com/destinations. Also the docs seem very clear about that.

We are currently looking at Segment, Jitsu and others. While we generally liked Jitsu, this was kind of a big deal for us and made us lean towards Segment.

However, no final decision has been made yet. ;-)

Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative

#108

Post by myowz »

alexdean wrote: post #95
reidalert wrote: post #26

Congrats on your launch, and looks really exciting! I'm curious how this compares to tools like Snowplow [1]? I guess Jitsu comes with more sources and destinations out of the box? [1] https://github.com/snowplow/snowplow

Snowplow CEO here. We haven't used Jitsu before but are very familiar with Segment. It looks like Jitsu sits in the Segment product family, along with Rudderstack: basically a Customer Data Platform bundle of simple JSON event tracking, Fivetran-style transactional/SaaS data ingest, and then relaying of data out to various SaaS endpoints plus cloud DWs. Snowplow started at the same time as Segment (2012) but has evol…

Alex - love your work on Snowplow.

Looking at Jitsu as a Snowplow familiar person I tried to do a quick browse of their marketing site and couldn’t find anything about their back end architecture. Was immediately thinking that wasn’t the focus here which is concerning when thinking about enterprise scalable data patterns.

Also appreciate you taking the high road “room for both” while the founder of Jitsu says “we are better”

I’ll stick with the product with a solid schema strategy, thank you…

Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative

#109

Post by fitzrocks »

ThePhysicist wrote: post #84
soumyadeb wrote: post #14

Earlier quoted context omitted.

Yes, RudderStack is not YC funded. Though I have learnt a lot from YC (and PG) through the years and attribute our entrepreneurship to them. Founder of RudderStack here.

Ah sorry, I mixed you up with Freshpaint, which is actually a YC startup and Segment competitor that pivoted to their current business model.

hey! Co-founder of Freshpaint here. Yes, we're YC-backed along with Segment, so you're probably thinking of us. YC does often fund startups working on similar things.
Post reply on HN