Are there any examples on how the resultant SQL tables look like in postgres or clickhouse for a given event schema? I'd like to know how generic it is per event type (is it sth like (event id, blob), or tries to decompose each event field into a column - what about nested objects then, etc.)). Knowing this would greatly improve my understanding on reusability of jitsu for various event-collection tasks I may have.
Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative
91–100 of 114 posts
Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative
#92Are there any examples on how the resultant SQL tables look like in postgres or clickhouse for a given event schema? I'd like to know how generic it is per event type (is it sth like (event id, blob), or tries to decompose each event field into a column - what about nested objects then, etc.)). Knowing this would greatly improve my understanding on reusability of jitsu for various event-collection tasks I may have.
That's what the website missing indeed. We have a few words about that in docs, but it's still not enough https://jitsu.com/docs/internals/jitsu-server#mapping-step
Overall, Jitsu tries to decompose (aka flatten) JSON as deep as possible. E.g. {a: {b:1, c:2}} will become a_b=1, a_c=2. If column is missing, it will be created. We don't decompose arrays so far
Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative
#93Great work! It's funny that YC funded Segment as well as two direct Segment competitors (RudderStack is the other one, though I think they initially started with a different idea an pivoted to that afterwards), though given the size of YC this is probably expected and Segment is probably large enough to "deserve" some good smaller competition. As someone who also builds an open-core product (though not directly model…
I'm sure YC is out of Segment by now.
Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative
#94The black banners at the top and bottom of your website breaks scrolling on mobile.
Thanks, we will fix that!
Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative
#95Congrats 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 evolved along a separate tech tree. Micro-service architecture, cloud native, using Kinesis or Cloud Pub-Sub as the data transit, enrichment framework plus a Confluent-style schema registry supporting very rich and versioned JSON Schema-based event payloads. We are built by and for data platform teams; our open-source behavioral data engine doesn't have a UI (our commercial Behavioral Data Platform does). Hosted trial here https://try.snowplowanalytics.com/
Definitely room for both product families in the market! I'm sure Jitsu will do great.
Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative
#96what value does the airbyte / elt integration provide? Surely I could just run etls on airflow or similar on tables that jitsu generates?
Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative
#97Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative
#98How 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?
Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative
#99How 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
Re: Launch HN: Jitsu (YC S20) – Open-Source Segment Alternative
#100I miss the eventnative name :)