71–80 of 90 posts
It looks very promising and is something I wish to scale Quantale( https://quantale.io/ ) to, It's a project I am working on, which has very similar logic of adding data sources and make it available for data visualization. Congrats on your launch!
Earlier quoted context omitted.
Traceback (most recent call last): File "site-packages/urllib3/connectionpool.py", line 677, in urlopen File "site-packages/urllib3/connectionpool.py", line 392, in _make_request File "http/client.py", line 1252, in request File "http/client.py", line 1298, in _send_request File "http/client.py", line 1247, in endheaders File "http/client.py", line 1026, in _send_output File "http/client.py", line 966, in send File "…
Isn’t there a GitHub issue submission page?
I havent released this as OS yet, but I'll put a demo online shortly.
For datalakes, I've also implemented something that could be useful: check out duplexRsync: https://github.com/francoisp/duplexRsync. I'll try to reach out via email to make sure you guys see this.
cheers! best, F
I had a read through your docs but was unable to find any info on how you handle the sync of hard deletions from sources. We use Stitch at the moment and have found this to be a surprisingly hard problem to solve without binary log replication, and without full refreshes. For the moment we've ruled out binlogs as we use Aurora MySQL which requires you to binlog from the master , and tying my data warehouse replicatio…
We don’t today, we will tomorrow when we start working on CDC. You’re raising a good point with MySQL, we will need to take this limitation into account. Hopefully there is a workaround.
I had a read through your docs but was unable to find any info on how you handle the sync of hard deletions from sources. We use Stitch at the moment and have found this to be a surprisingly hard problem to solve without binary log replication, and without full refreshes. For the moment we've ruled out binlogs as we use Aurora MySQL which requires you to binlog from the master , and tying my data warehouse replicatio…
Earlier quoted context omitted.
Your pricing page does not have any prices so it's hard to tell. I'll definitely keep an eye on your progress though. Your connector as container approach is interesting although i think IT departments may have issues with an on prem solution that spawns other containers by itself. One more thing - how will you protect yourself from let's say AWS forking you and selling a managed airbyte version?
The pricing depends on the number of connectors you need (but not the volume of data), the features you use, and the SLA. We already saw that there was a great willingness to pay, so we’re not really worried about that part. We will learn a great deal about that next year. Our sole focus in 2021 is the open-source part of the project, and becoming the new standard to replicate data. Regarding cloud providers as AWS,…
It's not uncommon for even small companies to have as many as a dozen sources. This sort of pricing schema can hurt smaller companies with low data volume but many sources (think e-commerce, especially in the era of "headless").
The Open Source Fivetran alternative. Yay, it was about time! A simple license : MIT. Clear differentiation between free & paid plans. I am liking what I am seeing so far. One of our client is in advertising industry and is syncing data from 20 different API vendors to postgres. So I am one of your potential customer. However, there is a big problem I'm noticing with "Open source alternatives" lately on HN. I had to…
hey yclurker, Supabase founder here. I'm sorry we haven't delivered a better self-hosting experience. This is clearly something we could do better. As I mentioned in your link[1], we're targeting a release of our CLI in Q1 (last week of march). > its a been long time since their launch It has been 8 months since our alpha launch*, and just over 1 month since our beta. I hope that sets some context, because personally…
Earlier quoted context omitted.
The pricing depends on the number of connectors you need (but not the volume of data), the features you use, and the SLA. We already saw that there was a great willingness to pay, so we’re not really worried about that part. We will learn a great deal about that next year. Our sole focus in 2021 is the open-source part of the project, and becoming the new standard to replicate data. Regarding cloud providers as AWS,…
> The pricing depends on the number of connectors you need It's not uncommon for even small companies to have as many as a dozen sources. This sort of pricing schema can hurt smaller companies with low data volume but many sources (think e-commerce, especially in the era of "headless").