Overall, snowplow is a great product, but they build for more complicated data pipelines rather than EventNative. We want to keep things simple
220 karma · joined June 24, 2019
Overall, snowplow is a great product, but they build for more complicated data pipelines rather than EventNative. We want to keep things simple
RudderStack is focusing on replacing Segment.com completely, we focus only on a part of the problem: getting events to DWH. Also, we don't have a UI.
By narrowing down the focus, we think we can do a better job sending data to DWHs. One example: we automatically create SQL schema based on JSON structure. You can send
{ "any": { "custom": "a", "field": "b" } }
To EventNative and we'll create any_custom and any_field columns in DWH table on a fly.
Besides, if you want to data to land at BQ/CH or RedShift with Devlot, you'll need add a 3rd-party Kafka->DWH layer. I'm pretty sure there'are many oss options. Not sure if they can automatically generare SQL schema from JSON object like EventNative
The algo is a follows: a) check if ga / analytics object is present b) add interceptor c) if the code was fully loaded (not a stup), send "fake" pageview event (which has been already sent), intercept it and send to EN backend only (not the original backend).
Also, we received a pull request that won't require EN code be inserted after GA/Segment. It tries to get window.ga/analytics object. If it doesn't exist, try the same thing in 1 second via setTimeout. We most likely with merge it to master soon
Re: materialized views - since not all DWH support them, we're not sure how can we leverage them. However, what do you have in mind? Maybe we're wrong!