5 ms·
I saw this project a few months ago and I'm really surprised how fast they've been adding new connectors [1]. I was initially a little doubtful about them imple
by sdepablos 6y ago
I saw this project a few months ago and I'm really surprised how fast they've been adding new connectors [1]. I was initially a little doubtful about them implementing their own protocol [2] instead of using Singer [3], already OOS, but it looks like it panned out for them. In fact I've been using Stitch Data for a couple of years and I've find myself "fighting" with their support team about bugs I think we're Singer related, mainly with DDL commands.
[1] https://docs.airbyte.io/changelog/connectors https://docs.airbyte.io/changelog/connectors
[2] https://airbyte.io/articles/data-engineering-thoughts/why-you-should-not-build-your-data-pipeline-on-top-of-singer/ https://airbyte.io/articles/data-engineering-thoughts/why-yo...
[3] https://www.singer.io/ https://www.singer.io/
- glogla 6y agoIf you don't mind me asking, how does Stitch scale? We're currently using bespoke Spark-based ETL tool because we need to move like 2 TB/day from various place, especially legacy system that don't make incremental data movement practical. How does Stitch even run, all SaaS in Stich Cloud or something? Thanks!
- sdepablos 6y agoPure SaaS. Check their pricing [1], as is row based and depending on how much data you need to move it can easily go out of budget ;) [1] https://www.stitchdata.com/pricing/ https://www.stitchdata.com/pricing/
- glogla 6y agoRight. Not something we can use then, since we can't have our data moving through public internet for legal reasons. Thanks for the answer.