I got a question here. Today I want to recommend A...
# announcements
w
I got a question here. Today I want to recommend AirByte to our team as a data integration tool. But I was challenged that why not we use Sqoop or Flume as an option. But I only can say that AirByte can be used for many connectors not only for database but also for ReatAPI, CSV file, or even cloud service, such as google sheet, etc. Besides that, Is there anything I can say to convince our team to try AriByte?
j
What are the source and destination connectors you need? We’re adding almost one new connector a day now.
I will let the team reply regarding Sqoop or Flume, as I'm not very familiar with them. But at first glance, I would say this. The goal for us is to support the long tail of connectors (both sources and destinations). Sqoop seems to be very limited in connectors (Hadoop mostly). On Airbyte, you can start moving data in minutes (in a recurring way): just deploy it, connect your tools and select the resulting schema and frequency and you're done.
I'm guessing your reply needs to be adapted to your use case, so if you want, we can jump on a quick call so we understand your use case, and give you the best answer to that question
w
Sorry for the late reply. The source of our use case is some of the transactional databases, such as PostgreSQL and Mysql and CSV/Excel file. and the destination is the Hive data warehouse. We had some discussion after that with our team. The thing they thought is that think we don’t need too much connector for now in our case, so we don’t have to introduce a new tool to our architecture. But I had prepared a showcase of what AriByte can do for them and presented the architecture of AirByte. This did catch their attention and I think they know what I am jazzed about AriByte.
m
Is there anything else I can answer for you?